Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/22—Indexing; Data structures therefor; Storage structures
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/10—File systems; File servers
  • G06F16/18—File system types
  • G06F16/182—Distributed file systems
  • G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
  • G06F16/1827—Management specifically adapted to NAS
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/22—Indexing; Data structures therefor; Storage structures
  • G06F16/2228—Indexing structures
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/22—Indexing; Data structures therefor; Storage structures
  • G06F16/2228—Indexing structures
  • G06F16/2272—Management thereof

Definitions

• Computing devices are often used to communicate over a network such as the Internet.
• Network based services offered by a service provider are becoming more commonplace.
• Computing devices are frequently used to connect to a network based service, which can provide services such as storing searchable data to be used/retrieved by the computing devices or providing additional processing power to the computing devices.
• a network based service can provide services such as storing searchable data to be used/retrieved by the computing devices or providing additional processing power to the computing devices.
• users of computing devices typically need to choose a configuration and/or format for their data, so that their data can be indexed and stored by the network based service.
• Conventional approaches typically require users to determine an appropriate configuration for their data.
• Conventional approaches can also demand a format to which the user's data must comply, thereby requiring the users to convert their data to the format. This can be inconvenient, cumbersome, or difficult to users who want to use the network based service for storage and search, thereby reducing the overall user experience.
• FIG. 1 illustrates an example environment in which aspects of the various embodiments can be utilized
• FIG. 2 illustrates an example system embodiment for index configuration for searchable data in a networked environment
• FIG. 3 illustrates an example web browsing environment in which index configuration for searchable data in a networked environment can be utilized
• FIG. 4 illustrates an example search index that can be generated in accordance with the various embodiments ;
• FIG. 5 illustrates an example method embodiment for index configuration for searchable data in a networked environment
• FIG. 6 illustrates an example device that can be used to implement aspects of the various embodiments
• FIG. 7 illustrates example components of a client device such as that illustrated in FIG. 6;
• FIG. 8 illustrates an environment in which various embodiments can be implemented.
• Systems and methods to generate an index configuration that can be used to generate a search index for data received over at least one network are described. At least some embodiments enable a computing device to upload data over a network (e.g., the Internet) onto a storage allocation provided by a network service (i.e., network service provider).
• the network service can analyze the uploaded data to determine a type of data field (i.e., data field type) for each data field in the plurality of data fields.
• the network service can analyze the uploaded data to determine whether or not to enable one or more search options for each data field in the plurality of data fields included in the uploaded data.
• At least some embodiments enable a computing device to upload data over a network (e.g., the Internet) onto a storage allocation provided by a network service (i.e., network service provider, network based service, etc.).
• a network service i.e., network service provider, network based service, etc.
• One or more users/entities e.g., using one or more computing devices
• the uploaded data can include a plurality of data fields.
• the network service can analyze the uploaded data to determine a type of data field (i.e., data field type) for each data field in the plurality of data fields.
• data field type i.e., data field type
• each data field can be of a type including an integer type, a text type, or a literal type.
• the network service can analyze the uploaded data to determine whether or not to enable one or more search options for each data field in the plurality of data fields included in the uploaded data. For example, the network service can determine, for each respective data field, whether or not to enable an option that would include the respective data field in a search index to be generated. The network service can also determine, for each respective data field, whether to enable an option that would calculate a facet count for the respective data field. Further, the network service can determine, for each respective data field, whether to enable an option that would return/provide the value associated with the respective data field in response to a search query.
• the network service can generate an index configuration (i.e., search index configuration, schema, index settings, etc.) for the data based at least in part on the determined data field type(s) and the search option(s) to be enabled.
• the network service can generate a search index for the data based at least in part on the index configuration.
• FIG. 1 illustrates an example environment 100 in which aspects of the various embodiments can be utilized.
• the example environment 100 can comprise at least one computing device 102, a network 104 (e.g., Internet, intranet, local network, local area network, etc.), and a network service 106 (i.e., network service provider, network based service, etc.).
• the at least one computing device 102 can be communicatively connected to the network service 106 over the network 104.
• the computing device 102 can communicate the network service 106 without a network 104 such as the Internet.
• the user or entity 108 can communicate data 110 from the at least one computing device 102 over the network 104 to the network service 106 (and vice versa).
• the network service 106 can comprise of and/or utilize one or more hosts or servers connected to the network 104.
• the network service 106 can rent storage space to customers, such as the user of the device 102 or another entity(ies) (e.g., company, organization, group, individual, etc.) 108.
• the user/entity 108 of the computing device 102 can store data from the device 102 onto the network service 106 using the network 104.
• the user/entity 108 and/or device 102 can utilize network based computing storage via the network service 106.
• the computing device 102 can transmit data 110 over the network 104 to be stored on the network service 106, as shown in FIG. 1.
• the data 110 can be any data utilized in network based computing, such as for search, database storage, running an application, running a virtual machine, running an operating system, etc.
• the computing device 102 can transmit the data 110 to be stored on a storage allocation provided by the service 106.
• the user/entity 108 can purchase or rent storage space on the service 106 and the storage allocation can be allocated and assigned to the user/entity 108.
• the user/entity 108 can have a particular account and/or storage allocation on the service 106; the storage space (e.g., storage allocation) allocated and assigned to the entity 108 can be associated with the account for the entity 108.
• the entity 108 may also want the network service 106 to provide a search index for the data 110.
• Conventional approaches typically require the entity 108 to first provide a configuration (i.e., index configuration, schema, index setting, etc.) for the data 110 to be indexed, or conventional approaches can require a configuration/format (e.g., Search Data Format (SDF)) that the entity's data 110 must comply with, thus demanding the entity 110 to convert its data 110 to the required configuration.
• SDF Search Data Format
• the entity 108 can transmit the data 110 to the network service 106, and the network service 106 can automatically (i.e., without an instruction or a request from the entity 108) analyze the data 110 and generate an index configuration (e.g., search index configuration, search index schema, etc.) for the data 110.
• the network service 106 can analyze the data 110 by determining a type of data field 112 for one or more data fields included in the data 110 and determining a search option 114 to be enabled for one or more data fields included in the data 110.
• the data 110 can include a plurality of data fields, each data field including a value (e.g., data field "name” can have a value of "ABCD-Brand Shirt”; data field “Price” can have a value of "$20' ; etc.).
• the network service 106 can analyze the plurality of data fields included in the data 110 to determine a data field type for each data field in the plurality.
• the network service 106 can determine whether the value of each respective data field comprises an amount of integers above a specified integer amount threshold (e.g., value of data field "Price" is all integers); if so, then that respective data field can be determined to be of an integer data field type.
• a specified integer amount threshold e.g., value of data field "Price" is all integers
• the network service 106 can also determine whether a data field is of a literal data field type by, for example, determining at least one of a value associated with the data field having an amount of alphabetic characters above a specified lower literal amount threshold but below a specified upper literal amount threshold, a number of distinct values associated with the data field being below a specified literal distinct amount threshold, a percentage of distinct values being below a specified literal distinct percentage threshold, or a length of values being below a specified literal length threshold.
• the network service 106 can, for example, consider the length of a data field value and the frequency and/or percentage of distinct values in the data field value to identify the data field as being of a text type; if there are many distinct values in a data field value and the data field value is very long (e.g., has a number of alphanumeric characters above a threshold), then the data field is likely of a text type. In some embodiments, if a data field is not of an integer type or a literal type, then the data field can be of a text type.
• the network service 106 can determine one or more search options 114 to be enabled for (the data fields of) the data 110. For example, having determined a data field type for a data field included in the data 110, the network service 106 can determine whether or not to enable an option to include the data field in the search index to be generated, whether or not to enable an option to calculate a facet count for the data field, and/or whether or not to enable an option to return/provide a search value for the data type.
• the network service 106 can choose the option not to include the data field (and value) in the search index.
• the network service 106 can choose to enable the option to include the data field in the search index to be generated, and the service 106 can enable the option to calculate a facet count for the data field.
• a facet count can be a count of how many search results fall into a certain category for a data field.
• the network service 106 can determine that it makes sense to provide a facet count, which indicates how many search results are associated with a certain category; e.g., "1984 (23), 2002 (12), 2010 (18)" shows an example of facet counts in which 23 search results are associated with "1984" with respect to the "Production Year” data field, 12 search results are associated with "2002,” and 18 search results are associated with "2010.”
• the network service 106 can also decide to enable the return of the value for a data field. For example, not all searchable data fields (and values) need to be returned (e.g., retrieved and presented) in response to a search request. The network service 106 can decide whether or not to return the value for a data field.
• the network service can automatically (i.e., without an instruction from the entity 108) generate a configuration (e.g., search index configuration, schema, etc.) for the data 110.
• the configuration can, at least in part, help determine how to index the data 110; the index configuration can, at least in part, govern how the data 110 will be indexed.
• the configuration or schema can specify a data field type for each data field included in the data 110, indicate whether each data field is searchable, indicate whether each data field is rankable (e.g., sortable), and other similar information useful for building the index.
• the network service 106 can generate a search index for the data 110 based in at least part on the generated configuration.
• FIG. 2 illustrates an example web browsing environment 200 in which index configuration for searchable data in a networked environment can be utilized.
• the example web browsing environment 200 can comprise an example web page 202 being rendered by an application, such as a web browser.
• the web page 202 can be provided by a network service that is associated with the domain, ABCD.com.
• a user/entity e.g., customer of the network service
• the data can be indexed and stored by the network service and made searchable to others such as potential customers of the user/entity.
• the network service can analyze the data to determine a type of data field (i.e., data field type) for each of the data fields included in the data.
• the data related to the selling of shirts can include data fields such as "Color” 206, "Size” 208, "Price” 210, "Description,” and other fields.
• the network service can analyze the value for each data field to determine a type for each respective data field.
• the network service can also determine one or more options (e.g., search options) to enable for each data field.
• the network service can subsequently generate a configuration/schema for the data to be indexed. Then the network service can generate an index for the data based on the configuration/schema.
• the network service can identify the data field "Color” and determine that its value (e.g., "Red,” “Blue,” “White,” “Green,” etc.) is alphabetic/literal and may identity the type of the "Color” data field to be a literal type.
• the data associated with the "Color” data field and the values e.g., "Red,” “Blue,” “White,” “Green,” etc.
• the network service can identify a "Size” data field in at least a portion of the uploaded data and determine that the values contained in the "Size” data field are numeric values. In this instance, the network service may determine that the "Size” data field is an integer type.
• the network service can identify the values for the "Description" data fields in at least a portion of the uploaded data and may determine that the values include both numbers and alphabetic characters, and/or that the values are lengthy in terms of the number of characters, and/or that the values have distinct terms/phrases/symbols. In this instance, the network service may determine that the "Description" data field is a text type.
• the network service can determine, for each of the data fields, whether to not to enable the option to include a respective data field in the search index to be generated. For example, in some embodiments, the "Description" data fields (and corresponding values) can be omitted from the search index. If so, then when a query is run with respect the search index, the query will not search the "Description" data field. However, some embodiments can and do include the "Description" data fields and values in the search index.
• the network service can determine whether or not to enable the option to calculate a facet count for each data field.
• a facet count represents how many of the results matching a search query have a particular value (or range of values) for a particular data field. For example, as shown in FIG. 2, the "Color" data field with a value of "Red” has a facet count of 23 (i.e., 23 search results for a "Red” shirt), whereas the "Blue” value of the "Color” data field has a facet count of 28 (i.e., 28 search results for a "Blue” shirt), and so forth.
• the values can overlap (i.e., do not have to be an exact match).
• a shirt with blue and red stripes can be associated with both the "Blue” and “Red” values, and/or with other values.
• the network service can determine that facet counts should be calculated for some of the data fields, but not necessarily all of the data fields. For example, the network service can determine that there should be facet counts for "Color,” “Size,” and “Price,” but not for "Description.”
• the network service can determine whether or not to enable a return of the value for a data field.
• a data field "Internal Product Identification Number” included in the data, the value of the data field being a product identification number internal to the entity and not intended to be shown to a customer of the entity; as such, the network service can determine not to enable a return of the value for such a data field.
• the network service can determine whether or not to enable an option to make a data field rankable (e.g., sortable).
• a data field rankable e.g., sortable
• the "Price” data field can be ranked/sorted by its values (e.g., from lowest price to highest price, from highest price to lowest price, etc.), the "Color” data field can be sorted alphabetically (not illustrated in FIG. 2), and so forth.
• there can be data related to media files such as music, videos, books, photographs, etc.
• Example data fields for the media files can include, but are not limited to, "Title,” “Artist/Author,” “Year Created,” “Price,” “Rating,” etc.
• the network service can generate a configuration (i.e., search index configuration, schema, etc.) for the data, the generating of the configuration being based at least in part on the determined data field types and search options.
• a configuration i.e., search index configuration, schema, etc.
• the network service can generate a search index for the data based at least in part on the generated configuration. Accordingly, the data provided by the entity can be stored with the network service and the search index for the data generated by the network service.
• FIG. 3 illustrates an example system embodiment 300 for index configuration for searchable data in a networked environment.
• the example system embodiment 300 can comprise a system controller 302, at least one communication transceiver 304, a data field type analyzer 306, a search option analyzer 308, an index configuration generator 310, an index generator 312, and at least one storage allocation 314.
• the system controller 302 can facilitate the system to perform various operations for index configuration for searchable data in a networked environment.
• the system controller 302 can communicate with the at least one communications transceiver 304 to facilitate data transmission to and/or data receipt from one or more sources external to the system 300 as well as to facilitate data communication among the system.
• Data received (e.g., from an entity) by the system 300 via the communications transceiver 304 can be analyzed by the data field type analyzer 306 to determine a type associated with each of the data fields included in the data.
• the data can also be analyzed by the search option analyzer 308 to determine whether or not to enable one or more search options with respect to each of the data fields included in the data.
• the index configuration generator 310 can generate a search index configuration/schema.
• the index generator 312 can generate a search index for the data.
• the data and the search index generated for the data can be stored on one or more storage allocations 314.
• the various components and/or portions of the example system 300 can be implemented as hardware, software, or a combination of both.
• the various parts of the system 300 can be implemented via a circuit, a processor, an application, a portion of programming code, an algorithm, or any combination thereof, etc.
• FIG. 3 is an example and meant to be used for illustrative purposes only.
• the various components do not have to be configured according to FIG. 3.
• the various components do not have to be tightly coupled to one another and can instead be spread across a more distributed system.
• a component such as the index generator can reside on a separate/different network and/or system, but still retain a communicative connection(s) to the other components.
• FIG. 4 illustrates an example search index 400 that can be generated in accordance with the various embodiments of the present disclosure.
• a root node 402 in the search index.
• data can be uploaded by an entity such as a T-Shirt retailer.
• the data can correspond to information about the T-Shirts (root node 402) that the entity has made available for sale.
• parent nodes e.g., 404, 406, 408 that represent data fields for the data relating to the T-Shirts.
• the T-Shirts can have a Color data field 404, a Size data field 406, and a Price data field 408.
• the data fields can have child nodes (e.g., 410, 412, 414, 416, 418) that represent values within each respective data field. For example, there can be at least two Colors (Red 410 and Blue 412), one Size (Medium 414), and two Price ranges ( ⁇ $10 416 and $ 10-$20 418). There can also be a set of search results/items (e.g., T-Shirts 420, 422, 424, 426,428, 430) that can correspond to one or more of the data fields and values.
• child nodes e.g., 410, 412, 414, 416, 418) that represent values within each respective data field.
• There can also be a set of search results/items e.g., T-Shirts 420, 422, 424, 4
• all three data fields (Color 404, Size 406, and Price 408) are to be included in the search index, can have facet counts, and can provide/return values in response to relevant search queries.
• Color:Red 410 can have a facet count of three and Color:Blue 412 can have a facet count of two.
• Size:Medium 414 can have a facet count of two.
• Price: ⁇ $10 416 can have a facet count of one and Price:$10-$20 418 can have a facet count of two.
• a search query of Color:Red 410 will return T-Shirts 422, 424, and 428; searching for Red 410 and Blue 412, for example, will return T-Shirt 422; and so forth.
• the example search index 400 is shown as a being a tree structure, it is contemplated that the search index can be generated in many other ways and/or with other structures.
• FIG. 5 illustrates an example method embodiment 500 for index configuration for searchable data in a networked environment.
• the example method embodiment 500 can receive data to be indexed.
• the method 500 can receive data, uploaded by an entity, to be indexed and the data can include a plurality of data fields (or at least one data field).
• the example method can also determine a name for a data field associated with the data.
• the example method 500 can determine a type of a data field associated with the data.
• the method can determine a field type, of a plurality of field types, associated with each data field in the plurality of data fields.
• the plurality of field types can include (but is not limited to) at least one of an integer type, a literal type, or a text type.
• the type of the data field can be determined from a plurality of types of data fields.
• the plurality of data fields and their types and/or names can be identified based on tags, signals, or other indications.
• the method 500 can determine one or more search options to be enabled with respect to the data field associated with the data, at step 506.
• the one or more search options can include at least one of an option to include a respective data field in a search index to be generated, an option to calculate a facet count for the respective data field, or an option to provide one or more values associated with the respective data field.
• Step 508 can include generating an index configuration for the data based at least in part on the type of the data field and the one or more search options.
• the method 500 can generate a search index for the data based at least in part on the index configuration for the data.
• the search index can be generated based on whether the data is structured data, free text data, or a combination of both.
• the example method can also provide at least one of the data, the index configuration, or the index to be searchable by one or more search queries.
• index configurations can hold information regarding whether a data field is facetable or not (i.e., whether or not a facet count should be calculated for the data field), whether a data field is rankable or not (i.e., whether or not the values of search results having the data field should be sorted), etc.
• the network service can convert data received/uploaded in a first format to a second format, the second format being compatible with the search index and can store the data converted to the second format on one or more storage allocations.
• the network service can receive data from the entity, the data capable of having any one or more of several various formats, such as .PDF, .DOC, .DOCX, .CSV, JSON, .XML, etc.
• the network service can automatically convert the data into a format compatible with (e.g., recognizable by, workable with, etc.) the network service, such as the Search Data Format (SDF).
• SDF Search Data Format
• the network service can covert the data based on comparing the first format with the second format and modifying at least one data field associated with the first format to correspond to at least one data field associated with the second format. For example, the network service can compare a format(s) of the data received from the entity and modify/update the format such that it is compatible with the network service. This can include identifying whether one or more data fields in the format should be added, removed, or changed.
• the network service can determine a type of a data field to be the integer type based on determining that a value associated with the data field has an amount of integer characters above a specified integer amount threshold. Also, the network service can determine a type of a data field to be the literal type determining at least one of a value associated with the data field having an amount of alphabetic characters above a specified lower literal amount threshold but below a specified literal amount threshold, a number of distinct values associated with the data field being below a specified literal distinct amount threshold, a percentage of distinct values being below a specified literal distinct percentage threshold, or a length of values being below a specified literal length threshold.
• the network service can determine a type of a data field to be the text type based on determining that a value associated with the data field has at least one of an amount of integer and alphabetic characters above a specified text amount threshold, a number of distinct characters above a specified text distinct amount threshold, a percentage of distinct characters above a specified text distinct percentage threshold, or a length of characters above a specified text length threshold.
• the network service can decide to enable the option to include a data field in a search index to be generated, the decision being based at least in part on receiving a signal included in the data field indicating that the data field is to be included in the search index.
• the network service can also decide to enable the option to calculate a facet count for a data field, the decision being based at least in part on determining that a quantity for at least one value associated with the data field is above a specified facet count lower threshold and below a specified facet count upper threshold.
• the network service can further decide to enable the option to provide a value associated with a data field in response to a relevant search query, the decision being based at least in part on receiving a signal included in the data field indicating that the value associated with the data field is to be provided.
• one or more search queries can be utilized by the network service.
• the network service can infer from the search queries that a searcher is faceting on a particular data field.
• the network service can determine that the data field should be of a literal type, for example.
• one or more search results can be presented in a particular rank expression (e.g., order of results), such as by relevance.
• rank expression e.g., order of results
• the present disclosure can allow for creations more complicated rank expressions that take into account other factors such as query independent factors (e.g., there can be a popularity data field included within the data, etc.).
• the present disclosure can also allow for analysis to propose rank expressions that can be used, by looking at the data and determining that a data field is meaningful in terms of popularity. For example, there can be a text body data field type and its length (e.g., or the inverse of its length) can be taken into account and can provide useful information for rank expressions.
• data field types can also include a geolocation type, a time type, a date type, or a floating point number type.
• Various embodiments consistent with the present disclosure can also utilize sample data.
• the user/entity can first provide sample data to the network service.
• the network service can analyze the sample data to determine types of data fields and search options. Based on the data field types and search options for the sample data, the network service can generate an index configuration, and subsequently generate a search index based on the generated index configuration.
• FIG. 6 illustrates an example electronic user device 600 that can be used in accordance with various embodiments.
• a portable computing device e.g., an electronic book reader or tablet computer
• any electronic device capable of receiving, determining, and/or processing input can be used in accordance with various embodiments discussed herein, where the devices can include, for example, desktop computers, notebook computers, personal data assistants, smart phones, video gaming consoles, television set top boxes, and portable media players.
• a computing device 600 can be an analog device, such as a device that can perform signal processing using operational amplifiers.
• the computing device 600 has a display screen 602 on the front side, which under normal operation will display information to a user facing the display screen (e.g., on the same side of the computing device as the display screen).
• the computing device in this example includes at least one camera 604 or other imaging element for capturing still or video image information over at least a field of view of the at least one camera.
• the computing device might only contain one imaging element, and in other embodiments the computing device might contain several imaging elements.
• Each image capture element may be, for example, a camera, a charge- coupled device (CCD), a motion detection sensor, or an infrared sensor, among many other possibilities. If there are multiple image capture elements on the computing device, the image capture elements may be of different types.
• At least one imaging element can include at least one wide-angle optical element, such as a fish eye lens, that enables the camera to capture images over a wide range of angles, such as 180 degrees or more.
• each image capture element can comprise a digital still camera, configured to capture subsequent frames in rapid succession, or a video camera able to capture streaming video.
• the example computing device 600 also includes at least one microphone 606 or other audio capture device capable of capturing audio data, such as words or commands spoken by a user of the device.
• a microphone 606 is placed on the same side of the device as the display screen 602, such that the microphone will typically be better able to capture words spoken by a user of the device.
• a microphone can be a directional microphone that captures sound information from substantially directly in front of the microphone, and picks up only a limited amount of sound from other directions. It should be understood that a microphone might be located on any appropriate surface of any region, face, or edge of the device in different embodiments, and that multiple microphones can be used for audio recording and filtering purposes, etc.
• the example computing device 600 also includes at least one orientation sensor 608, such as a position and/or movement-determining element.
• a sensor can include, for example, an accelerometer or gyroscope operable to detect an orientation and/or change in orientation of the computing device, as well as small movements of the device.
• An orientation sensor also can include an electronic or digital compass, which can indicate a direction (e.g., north or south) in which the device is determined to be pointing (e.g., with respect to a primary axis or other such aspect).
• An orientation sensor also can include or comprise a global positioning system (GPS) or similar positioning element operable to determine relative coordinates for a position of the computing device, as well as information about relatively large movements of the device.
• GPS global positioning system
• Various embodiments can include one or more such elements in any appropriate combination.
• the algorithms or mechanisms used for determining relative position, orientation, and/or movement can depend at least in part upon the selection of elements available to the device.
• FIG. 7 illustrates a logical arrangement of a set of general components of an example computing device 700 such as the device 600 described with respect to FIG. 6.
• the device includes a processor 702 for executing instructions that can be stored in a memory device or element 704.
• the device can include many types of memory, data storage, or non- transitory computer-readable storage media, such as a first data storage for program instructions for execution by the processor 702, a separate storage for images or data, a removable memory for sharing information with other devices, etc.
• the device typically will include some type of display element 706, such as a touch screen or liquid crystal display (LCD), although devices such as portable media players might convey information via other means, such as through audio speakers.
• LCD liquid crystal display
• the device in many embodiments will include at least one image capture element 708 such as a camera or infrared sensor that is able to image projected images or other objects in the vicinity of the device.
• image capture can be performed using a single image, multiple images, periodic imaging, continuous image capturing, image streaming, etc.
• a device can include the ability to start and/or stop image capture, such as when receiving a command from a user, application, or other device.
• the example device similarly includes at least one audio capture component 712, such as a mono or stereo microphone or microphone array, operable to capture audio information from at least one primary direction.
• a microphone can be a uni-or omnidirectional microphone as known for such devices.
• the computing device 700 of FIG. 7 can include one or more communication elements (not shown), such as a Wi-Fi, Bluetooth, RF, wired, or wireless communication system.
• the device in many embodiments can communicate with a network, such as the Internet, and may be able to communicate with other such devices.
• the device can include at least one additional input device able to receive conventional input from a user.
• This conventional input can include, for example, a push button, touch pad, touch screen, wheel, joystick, keyboard, mouse, keypad, or any other such device or element whereby a user can input a command to the device.
• such a device might not include any buttons at all, and might be controlled only through a combination of visual and audio commands, such that a user can control the device without having to be in contact with the device.
• the device 700 also can include at least one orientation or motion sensor 710.
• a sensor can include an accelerometer or gyroscope operable to detect an orientation and/or change in orientation, or an electronic or digital compass, which can indicate a direction in which the device is determined to be facing.
• the mechanism(s) also (or alternatively) can include or comprise a global positioning system (GPS) or similar positioning element operable to determine relative coordinates for a position of the computing device, as well as information about relatively large movements of the device.
• GPS global positioning system
• the device can include other elements as well, such as may enable location determinations through triangulation or another such approach. These mechanisms can communicate with the processor 702, whereby the device can perform any of a number of actions described or suggested herein.
• a computing device such as that described with respect to FIG. 6 can capture and/or track various information for a user over time.
• This information can include any appropriate information, such as location, actions (e.g., sending a message or creating a document), user behavior (e.g., how often a user performs a task, the amount of time a user spends on a task, the ways in which a user navigates through an interface, etc.), user preferences (e.g., how a user likes to receive information), open applications, submitted requests, received calls, and the like.
• the information can be stored in such a way that the information is linked or otherwise associated whereby a user can access the information using any appropriate dimension or group of dimensions.
• FIG. 8 illustrates an example of an environment 800 for implementing aspects in accordance with various embodiments.
• the system includes an electronic client device 802, which can include any appropriate device operable to send and receive requests, messages or information over an appropriate network 804 and convey information back to a user of the device.
• client devices include personal computers, cell phones, handheld messaging devices, laptop computers, set-top boxes, personal data assistants, electronic book readers and the like.
• the network can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network or any other such network or combination thereof. Components used for such a system can depend at least in part upon the type of network and/or environment selected. Protocols and components for communicating via such a network are well known and will not be discussed herein in detail. Communication over the network can be enabled via wired or wireless connections and combinations thereof.
• the network includes the Internet, as the environment includes a Web server 806 for receiving requests and serving content in response thereto, although for other networks an alternative device serving a similar purpose could be used, as would be apparent to one of ordinary skill in the art.
• the illustrative environment includes at least one application server 808 and a data store 810. It should be understood that there can be several application servers, layers or other elements, processes or components, which may be chained or otherwise configured, which can interact to perform tasks such as obtaining data from an appropriate data store.
• data store refers to any device or combination of devices capable of storing, accessing and retrieving data, which may include any combination and number of data servers, databases, data storage devices and data storage media, in any standard, distributed or clustered environment.
• the application server can include any appropriate hardware and software for integrating with the data store as needed to execute aspects of one or more applications for the client device and handling a majority of the data access and business logic for an application.
• the application server provides access control services in cooperation with the data store and is able to generate content such as text, graphics, audio and/or video to be transferred to the user, which may be served to the user by the Web server in the form of HTML, XML or another appropriate structured language in this example.
• content such as text, graphics, audio and/or video to be transferred to the user, which may be served to the user by the Web server in the form of HTML, XML or another appropriate structured language in this example.
• the handling of all requests and responses, as well as the delivery of content between the client device 802 and the application server 808, can be handled by the Web server 806. It should be understood that the Web and application servers are not required and are merely example components, as structured code discussed herein can be executed on any appropriate device or host machine as discussed elsewhere herein.
• the data store 810 can include several separate data tables, databases or other data storage mechanisms and media for storing data relating to a particular aspect.
• the data store illustrated includes mechanisms for storing production data 812 and user information 816, which can be used to serve content for the production side.
• the data store also is shown to include a mechanism for storing log or session data 814. It should be understood that there can be many other aspects that may need to be stored in the data store, such as page image information and access rights information, which can be stored in any of the above listed mechanisms as appropriate or in additional mechanisms in the data store 810.
• the data store 810 is operable, through logic associated therewith, to receive instructions from the application server 808 and obtain, update or otherwise process data in response thereto.
• a user might submit a search request for a certain type of element.
• the data store might access the user information to verify the identity of the user and can access the catalog detail information to obtain information about elements of that type.
• the information can then be returned to the user, such as in a results listing on a Web page that the user is able to view via a browser on the user device 802.
• Information for a particular element of interest can be viewed in a dedicated page or window of the browser.
• Each server typically will include an operating system that provides executable program instructions for the general administration and operation of that server and typically will include computer-readable medium storing instructions that, when executed by a processor of the server, allow the server to perform its intended functions.
• Suitable implementations for the operating system and general functionality of the servers are known or commercially available and are readily implemented by persons having ordinary skill in the art, particularly in light of the disclosure herein.
• the environment in one embodiment is a distributed computing environment utilizing several computer systems and components that are interconnected via communication links, using one or more computer networks or direct connections.
• a distributed computing environment utilizing several computer systems and components that are interconnected via communication links, using one or more computer networks or direct connections.
• FIG. 8 it will be appreciated by those of ordinary skill in the art that such a system could operate equally well in a system having fewer or a greater number of components than are illustrated in FIG. 8.
• the depiction of the system 800 in FIG. 8 should be taken as being illustrative in nature and not limiting to the scope of the disclosure.
• the various embodiments can be implemented in a wide variety of operating environments, which in some cases can include one or more user computers, computing devices, or processing devices which can be used to operate any of a number of applications.
• User or client devices can include any of a number of general purpose personal computers, such as desktop or laptop computers running a standard operating system, as well as cellular, wireless, and handheld devices running mobile software and capable of supporting a number of networking and messaging protocols.
• Such a system also can include a number of workstations running any of a variety of commercially-available operating systems and other known applications for purposes such as development and database management.
• These devices also can include other electronic devices, such as dummy terminals, thin-clients, gaming systems, and other devices capable of communicating via a network.
• Various aspects also can be implemented as part of at least one service or Web service, such as may be part of a service-oriented architecture.
• Services such as Web services can communicate using any appropriate type of messaging, such as by using messages in extensible markup language (XML) format and exchanged using an appropriate protocol such as SOAP (derived from the "Simple Object Access Protocol").
• SOAP derived from the "Simple Object Access Protocol”
• Processes provided or executed by such services can be written in any appropriate language, such as the Web Services Description Language (WSDL).
• WSDL Web Services Description Language
• Using a language such as WSDL allows for functionality such as the automated generation of client-side code in various SOAP frameworks.
• Most embodiments utilize at least one network that would be familiar to those skilled in the art for supporting communications using any of a variety of commercially- available protocols, such as TCP/IP, OSI, FTP, UPnP, NFS, CIFS, and AppleTalk.
• the network can be, for example, a local area network, a wide-area network, a virtual private network, the Internet, an intranet, an extranet, a public switched telephone network, an infrared network, a wireless network, and any combination thereof.
• the Web server can run any of a variety of server or mid-tier applications, including HTTP servers, FTP servers, CGI servers, data servers, Java servers, and business application servers.
• the server(s) also may be capable of executing programs or scripts in response requests from user devices, such as by executing one or more Web applications that may be implemented as one or more scripts or programs written in any programming language, such as Java®, C, C# or C++, or any scripting language, such as Perl, Python, or TCL, as well as combinations thereof.
• the server(s) may also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, and IBM®.
• the environment can include a variety of data stores and other memory and storage media as discussed above. These can reside in a variety of locations, such as on a storage medium local to (and/or resident in) one or more of the computers or remote from any or all of the computers across the network. In a particular set of embodiments, the information may reside in a storage-area network ("SAN") familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers, servers, or other network devices may be stored locally and/or remotely, as appropriate.
• SAN storage-area network
• each such device can include hardware elements that may be electrically coupled via a bus, the elements including, for example, at least one central processing unit (CPU), at least one input device (e.g., a mouse, keyboard, controller, touch screen, or keypad), and at least one output device (e.g., a display device, printer, or speaker).
• CPU central processing unit
• input device e.g., a mouse, keyboard, controller, touch screen, or keypad
• at least one output device e.g., a display device, printer, or speaker
• Such a system may also include one or more storage devices, such as disk drives, optical storage devices, and solid-state storage devices such as random access memory (“RAM”) or read-only memory (“ROM”), as well as removable media devices, memory cards, flash cards, etc.
• ROM read-only memory
• Such devices can include a computer-readable storage media reader, a communications device (e.g., a modem, a network card (wireless or wired), an infrared communication device, etc.), and working memory as described above.
• the computer- readable storage media reader can be connected with, or configured to receive, a computer-readable storage medium, representing remote, local, fixed, and/or removable storage devices as well as storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information.
• the system and various devices also typically will include a number of software applications, modules, services, or other elements located within at least one working memory device, including an operating system and application programs, such as a client application or Web browser.
• Storage media and computer readable media for containing code, or portions of code can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the a system device.
• RAM random access memory
• ROM read only memory
• EEPROM electrically erasable programmable read-only memory
• flash memory electrically erasable programmable read-only memory
• CD-ROM compact disc read-only memory
• DVD digital versatile disk
• magnetic cassettes magnetic tape
• magnetic disk storage magnetic disk storage devices
• a computer-implemented method for index configuration for searchable data in a networked environment comprising:
• receiving data to be indexed the data including a plurality of data fields; determining a name associated with each data field in the plurality of data fields;
• the one or more search options including at least one of an option to include a respective data field in a search index to be generated, an option to calculate a facet count for the respective data field, or an option to provide one or more values associated with the respective data field;
• a computer-implemented method comprising:
• the type of the data field being determined from a plurality of types of data fields
• determining the type of the data field to be the integer type.
• determining the type of the data field to be the text type.
• the one or more search options include at least one of an option to include the data field in the search index to be generated, an option to calculate a facet count for the data field, or an option to provide a value associated with the data field in response to a relevant search query.
• a 13 The computer-implemented method of clause A 12, wherein the determining the one or more search options to be enabled comprises deciding to enable the option to include the data field in the search index to be generated, the decision being based at least in part on at least one of receiving a signal included in the data field indicating that the data field is to be included in the search index or determining a type of the data field to be a literal type.
• the determining the one or more search options to be enabled comprises deciding to enable the option to calculate the facet count for the data field, the decision being based at least in part on determining that a quantity for a distribution of a plurality of values associated with the data field is below a specified facet count upper threshold.
• a 15 The computer-implemented method of clause A 12, wherein the determining the one or more search options to be enabled comprises deciding to enable the option to provide the value associated with the data field in response to the relevant search query, the decision being based at least in part on at least one of receiving a signal included in the data field indicating that the value associated with the data field is to be provided or determining that a length of the value associated with the data field is below a specified return value length threshold.
• a system comprising:
• At least one communications transceiver At least one communications transceiver
• a memory device including instructions that, when executed by the at least one processor, cause the system to:
• the type of the data field being determined from a plurality of types of data fields; determine one or more search options to be enabled with respect to the data field associated with the data;
• a 19 The system of clause Al 8, wherein the data is of a first format, and wherein the instructions cause the system to further:
• a non-transitory computer-readable storage medium including instructions for identifying elements, the instructions when executed by a processor of a computing system causing the computing system to:
• the type of the data field being determined from a plurality of types of data fields
• A23 The non-transitory computer-readable storage medium of clauseA 22, wherein the instructions cause the computing system to determine the type of the data field to be the literal type based on determining at least one of a value associated with the data field having an amount of alphabetic characters above a specified lower literal amount threshold but below a specified upper literal amount threshold, a number of distinct values associated with the data field being below a specified literal distinct amount threshold, a percentage of distinct values being below a specified literal distinct percentage threshold, or a length of values being below a specified literal length threshold.
• search options include at least one of an option to include the data field in the search index to be generated, an option to calculate a facet count for the data field, or an option to provide a value associated with the data field in response to a relevant search query.
• determining the one or more search options to be enabled comprises deciding to enable the option to calculate the facet count for the data field, the decision being based at least in part on determining that a quantity for at least one value associated with the data field is above a specified facet count lower threshold and below a specified facet count upper threshold.
• monitoring at least one of an amount of data being stored or a rate at which data is being manipulated on a first partition provided by a network service, the first partition being included in a storage allocation provided by the network service; detecting that the at least one of the amount or the rate exceeds a specified amount threshold or a specified rate threshold, respectively;
• a computer-implemented method comprising:
• the storage allocation having a number of partitions including at least one partition
• modifying the at least one of the size or the number is based on at least one of the data usage on the storage allocation or the determined CPU usage of the storage allocation.
• modifying a configuration of the storage allocation based on at least one of a configuration associated with the data usage or a user- initiated input.
• a system comprising:
• a storage allocation having a number of partitions including at least one partition
• a memory device including instructions that, when executed by the at least one processor, cause the system to:
• At least one load balancer configured to facilitate in the network traffic being directed away from the portion of the storage allocation during the modifying the at least one of the size or the number and in the network traffic being directed to the portion of the storage allocation when the modifying the at least one of the size or the number is complete.
• At least one monitor module configured to facilitate in the monitoring the data usage on the storage allocation and in the determining whether the data usage on the at least one partition included in the storage allocation exceeds a specified threshold.
• a non-transitory computer-readable storage medium including instructions for identifying elements, the instructions when executed by a processor of a computing system causing the computing system to:

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Data Mining & Analysis (AREA)
• Databases & Information Systems (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Software Systems (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Applications Claiming Priority (3)

Publications (2)

Family

ID=50477970

Family Applications (1)

Country Status (10)

Cited By (2)

Families Citing this family (25)

Family Cites Families (22)

• 2013
  • 2013-10-12 CN CN201380053433.7A patent/CN104823169B/zh active Active
  • 2013-10-12 IN IN3160DEN2015 patent/IN2015DN03160A/en unknown
  • 2013-10-12 BR BR112015008146A patent/BR112015008146A2/pt not_active Application Discontinuation
  • 2013-10-12 AU AU2013328901A patent/AU2013328901B2/en not_active Ceased
  • 2013-10-12 WO PCT/US2013/064731 patent/WO2014059394A1/en active Application Filing
  • 2013-10-12 SG SG11201502828PA patent/SG11201502828PA/en unknown
  • 2013-10-12 KR KR1020177012552A patent/KR101782302B1/ko active IP Right Grant
  • 2013-10-12 CA CA2888116A patent/CA2888116C/en active Active
  • 2013-10-12 CN CN201811424497.4A patent/CN110096502A/zh active Pending
  • 2013-10-12 SG SG10201606363SA patent/SG10201606363SA/en unknown
  • 2013-10-12 KR KR1020157012030A patent/KR101737246B1/ko active IP Right Grant
  • 2013-10-12 EP EP13845541.5A patent/EP2907034A4/de not_active Withdrawn
  • 2013-10-12 JP JP2015536973A patent/JP2015532493A/ja active Pending
• 2016
  • 2016-09-20 AU AU2016231488A patent/AU2016231488B2/en not_active Ceased
  • 2016-10-28 JP JP2016211567A patent/JP6339155B2/ja active Active
• 2017
  • 2017-10-12 AU AU2017245374A patent/AU2017245374B2/en not_active Ceased

Also Published As

Similar Documents

Legal Events