WO2018077138A1

WO2018077138A1 - Data configuration method, index management method, related apparatus and computing device

Info

Publication number: WO2018077138A1
Application number: PCT/CN2017/107343
Authority: WO
Inventors: 王楠楠; 刘若曦
Original assignee: 华为技术有限公司
Priority date: 2016-10-24
Filing date: 2017-10-23
Publication date: 2018-05-03
Also published as: CN107977381A; CN107977381B

Abstract

A data configuration method, for improving the search performance of a search system. The data configuration method comprises: receiving a plurality of search requests issued by a user, each search request among the plurality of search requests comprising one or more search fields for requesting to search for a document containing the search field(s); determining the field to which each search field, among the search fields comprised in the plurality of search requests, belongs, and determining therein one or more hotspot fields; adding the one or more hotspot fields into a schema configuration document, and updating the document in the search system according to the schema configuration document with the added hotspot fields. Further provided are an index management method, a related apparatus and a computing device.

Description

Data configuration method, index management method, related device, and computing device

Technical field

The present application relates to the field of data search, and in particular, to a data configuration method, an index management method, a related device, and a computing device.

Background technique

The full-text search technology is a general-purpose search technology at present, which is used to search for the required information according to the search field and the like as a search portal. With the rapid development of big data technology, user data is exploding, so the requirements for the efficiency and speed of full-text search technology are getting higher and higher.

Search systems relying on full-text search technology mainly include Solr, Elastic, etc. Among them, Solr is a popular enterprise search system, and its functions include full-text search, hit mark, faceted search, dynamic clustering, database integration, and rich text. (such as Word, PDF) processing. This application only uses Solr as an example to describe the search system.

The search system generally saves information by using a data file (English: document, abbreviation: doc) as a basic unit. The data in the doc is generally saved as a domain (English: field) + domain value structure, where the domain is used to indicate the type of the corresponding domain value, and the domain value is used to record the specific value of the corresponding domain.

The domain of the doc in the search system is defined by the field configuration (English: schema) configuration file. By defining different domains in the schema configuration file, domain-by-domain search can be implemented to improve search speed and efficiency.

However, the search system holds a huge amount of doc data, and the huge amount of doc data covers a larger number of domains. The current search system relies on the technicians manually setting multiple domains in the schema configuration file. Since the technician cannot know in advance which domain will be searched multiple times by the user, the set domain may be very likely in practical applications. Less search by users. As a result, the use frequency of the domain search function is not high, and the speed and efficiency improvement by the domain search is limited, and the search performance of the search system does not meet the user requirements.

Summary of the invention

The present application provides a data configuration method, an index management method, a related device, and a computing device for improving search performance of a search system.

The first aspect of the present application provides a data configuration method suitable for a search system. The search system includes multiple data files, and each data file includes one or more domains and domain values corresponding to the one or more domains. The domain is used to indicate the type of the corresponding domain value. The domain value is used to record the specific value of the corresponding domain. The search system also includes a schema configuration file for defining a domain of data files in the search system. The data configuration method includes: receiving a plurality of search requests issued by a user, wherein each of the plurality of search requests includes one or more search fields for requesting to search for a data file that includes the search field. Determining the domain to which each search field belongs in the search field included in the plurality of search requests, and determining one or more hotspot domains therein. Add the one or more hotspot domains to the schema configuration file and update the data files in the search system according to the schema configuration file to which the hotspot domain is added. In the data configuration method provided by this application, the domain in the schema configuration file It is not a domain set by the technician, but a hotspot domain determined by the search system according to the search request issued by the user immediately. Since the hotspot domain is a domain with a high search frequency in the search request, the hotspot domain has a high probability to be searched again by the user in the subsequent time. By adding a hotspot domain to the schema configuration file, the frequency of searching by domain can be increased, and the speed and efficiency of the domain search can be fully utilized to further improve the search performance of the search system.

Optionally, the multiple search requests may carry the domain described by the search field, where the response message of the multiple search requests carries the domain described by the search field. The search system determines, according to each search request and/or a response message corresponding to each search request, a domain to which each search field in the search field included in the plurality of search requests belongs.

Optionally, the search system extracts a domain field carried in the search request and/or the response message according to the interval identifier in each search request and/or the response message corresponding to each search request, and further determines the multiple search request locations. The domain to which each search field in the search field is included.

Optionally, the search system determines the domain in which each search field belongs, including the previous one or more domains with the most search fields as the hotspot domain.

Optionally, after determining that the one or more hotspot domains are included, the search system determines a domain value format of each hotspot domain according to a search field included in each hotspot domain in the one or more hotspot domains.

Optionally, the search system determines, in a format that the search fields included in each of the one or more hotspot domains are consistently matched, a domain value format for searching each hotspot domain.

Optionally, the search system counts the search data corresponding to each domain in the domain defined by the schema configuration file every domain value period. The search data includes one or more of the searched times, the searched frequency, and the search hit ratio of the corresponding domain in the current preset period. The search system deletes one or more domains in the schema configuration file whose search data is lower than the threshold to implement dynamic elimination of non-hotspot domains in the schema configuration file.

The second aspect of the present application provides an index management method suitable for a search system. The search system includes multiple data files, and each data file includes one or more domains and domain values corresponding to the one or more domains. The domain is used to indicate the type of the corresponding domain value. The domain value is used to record the specific value of the corresponding domain. The search system further includes a default index corresponding to the plurality of data files, where each default index includes a storage location of the corresponding data file in the search system, and the method includes: receiving a plurality of search requests sent by the user, the multiple In the search request, each search request includes one or more search fields for requesting to find a data file containing the search field. Determining the domain to which each search field belongs in the search field included in the plurality of search requests. The domain value format of each domain in the domain to which each search field belongs is determined according to the search field included in the domain to which each search field belongs. A data file containing a field conforming to the field value format is determined in the search system as the first data file. Generating a second data file corresponding to each of the first data files, where each second data file includes: a field corresponding to the field value format included in the corresponding first data file, and a field corresponding to the field value format Domain. A new index corresponding to each second data file is generated, and the new index includes a storage location of the corresponding second data file in the search system. When the search system receives the newly issued search request from the user, the search field in the search request has a high probability of hitting the new index generated by the index management device. Since the data volume of the newly created index is much smaller than the data volume of the default index, searching for the new index can greatly save the workload of the search system and improve the search speed and efficiency of the search system, and improve the search index. Search system search performance.

Optionally, the multiple search requests may carry the domain described by the search field, and the multiple search requests are ringing The message should carry the domain described in the search field. The search system determines, according to each search request and/or a response message corresponding to each search request, a domain to which each search field in the search field included in the plurality of search requests belongs.

Optionally, the search system determines a domain value format of each domain in the domain to which each search field belongs according to the search field included in each domain in the domain to which each search field belongs.

Optionally, the search system receives the target search request sent by the user, where the target search request includes a target search field, and is used to request to find a data file that includes the target search field. The search system finds a new index corresponding to the target search field. If the new index corresponding to the target search field is found, the data file containing the target search field is obtained according to the newly created index.

Optionally, if the search system does not find the new index corresponding to the target search field, the default index corresponding to the target search field is searched to obtain a data file that includes the target search field.

Optionally, when a new data file is imported into the search system, if the new data file includes a field that conforms to the domain value format, the search system generates a second data file corresponding to the new data file. The second data file corresponding to the generated new data file includes: a field in the new data file that conforms to the domain value format and a domain to which the field belongs. The search system creates a corresponding new index for the second data file corresponding to the new data file, including the storage location of the second data file corresponding to the new data file in the search system.

Optionally, the search system counts the search parameters of each new index every preset period. The search parameter of each new index includes one or more of the number of searched times, the searched frequency, and the search hit ratio of the domain corresponding to the new index in the current preset period. The search system deletes one or more new indexes whose search parameters are below the threshold to implement dynamic retirement of non-hotspot indexes in the newly created index.

The third aspect of the present application provides a data configuration apparatus suitable for a search system. The search system includes multiple data files, and each data file includes one or more domains and domain values corresponding to the one or more domains. The domain is used to indicate the type of the corresponding domain value. The domain value is used to record the specific value of the corresponding domain. The search system also includes a schema configuration file for defining a domain of data files in the search system. The data configuration apparatus includes: an information receiving module, configured to receive a plurality of search requests issued by the user, each of the plurality of search requests includes a search field, configured to request to find a data file that includes the search field. The domain determining module is configured to determine a domain to which each search field belongs in the search field included in the plurality of search requests. A hotspot determination module is configured to determine one or more hotspot domains in a domain to which each search field belongs. The configuration modification module is configured to add the one or more hotspot domains to the schema configuration file, and update the data files in the search system according to the schema configuration file to which the one or more hotspot domains are added. The domain in the schema configuration file of the present application is not a domain set by a technician, but is a hotspot domain determined by the data configuration device according to a search request sent by the user immediately. Since the hotspot domain is a domain with a higher search frequency among the N search requests, the hotspot domain has a high probability to be searched again by the user in the subsequent time. By adding a hotspot domain to the schema configuration file, the frequency of searching by domain can be increased, and the speed and efficiency of the domain search can be fully utilized to further improve the search performance of the search system. Data configuration device

Optionally, the domain determining module is specifically configured to: according to each search request, and/or a response message of the search system for each search request, determine a domain to which each search field in the search field included in the multiple search requests belongs .

Optionally, the domain determining module is specifically configured to: determine, according to each search request, and/or a search box in the response message of each search request, each search in the search field included in the multiple search requests. The domain to which the field belongs.

Optionally, the hotspot determining module is specifically configured to: determine, in the domain to which each search field belongs, the first one or more domains including the search field to be the hotspot domain.

Optionally, the data configuration apparatus further includes a format determining module, configured to determine a domain value format of each hotspot domain according to a search field included in each hotspot domain in the one or more hotspot domains.

Optionally, the format determining module is specifically configured to: determine, in a format that the search fields included in each hotspot domain in the one or more hotspot domains are consistent, a domain value format of each hotspot domain.

Optionally, the configuration modification module is further configured to: periodically search, in a preset period, search data of each domain in the domain defined by the schema configuration file, where the search data includes a domain defined by the schema configuration file in a current preset period. One or more of the number of searches, the frequency of search, and the search hit rate; delete one or more domains whose search data is below the threshold in the schema configuration file.

The fourth aspect of the present application provides an index management apparatus suitable for a search system. The search system includes multiple data files, and each data file includes one or more domains and domain values corresponding to the one or more domains. The domain is used to indicate the type of the corresponding domain value. The domain value is used to record the specific value of the corresponding domain. The search system further includes a default index corresponding to the plurality of data files, and each default index includes a storage location of the corresponding data file in the search system. The index management apparatus includes: a receiving information module, configured to receive a plurality of search requests issued by the user, where each of the plurality of search requests includes a search field for requesting to search for a data file that includes the search field. The determining domain module is configured to determine a domain to which each search field belongs in the search field included in the plurality of search requests. The determining format module is configured to determine a domain value format of each domain in a domain to which each search field belongs according to a search field included in each domain in a domain to which each search field belongs. And a file determining module, configured to determine, as the first data file, a data file in the search system that includes a field that conforms to the domain value format determined in the determining format module. a file generating module, configured to generate a second data file corresponding to each first data file, where each second data file includes a field corresponding to the field value format included in the corresponding first data file, and the domain conforms to the domain The domain to which the field of the value format belongs. The index management module is configured to generate a new index corresponding to each second data file, where the new index includes a storage location of the corresponding second data file in the search system. When the search system receives the newly issued search request from the user, the search field in the search request has a high probability of hitting the new index generated by the index management device. Since the data volume of the newly created index is much smaller than the data volume of the default index, searching for the new index can greatly save the workload of the search system and improve the search speed and efficiency of the search system, and improve the search index. Search system search performance.

Optionally, the determining domain module is specifically configured to: according to each search request, and/or a response message of the search system for each search request, determine a domain to which each search field in the search field included in the multiple search requests belongs .

Optionally, the determining domain module is specifically configured to: determine, according to each search request, and/or a search box in the response message of each search request, each search in the search field included in the multiple search requests. The domain to which the field belongs.

Optionally, the determining format module is specifically configured to determine, in a format that the search fields included in each domain in each domain of each search field are consistent, a domain value of each domain in the domain to which each search field belongs. format.

Optionally, the receiving information module is further configured to: receive a target search request sent by the user, and the target search request A target search field is included for requesting to find a data file containing the target search field.

The index management device further includes a file search module, configured to: search for a new index corresponding to the target search field; if the new index corresponding to the target search field is found, obtain the target search field according to the new index corresponding to the target search field. Data file.

Optionally, the file search module is further configured to: if the new index corresponding to the target search field is not found, look for a default index corresponding to the target search field.

Optionally, the file generating module is further configured to: when the new data file is imported in the search system, if the new data file includes a field that determines a format corresponding to the domain value determined by the format module, the new data file is generated. Corresponding second data file, the second data file corresponding to the new data file includes: a field in the new data file that conforms to the domain value format, and a field in the new data file that conforms to the domain value format Domain.

The index management module is further configured to: generate a new index corresponding to the second data file corresponding to the new data file, where the new index corresponding to the second data file corresponding to the new data file includes: a second corresponding to the new data file The location where the data file is saved in the search system.

Optionally, the index management module is further configured to: collect, according to a preset period, a search parameter of each new index, where the search parameter includes the number of times of searching, the frequency of search, and the search for each new index in the current preset period. One or more of the hit ratios; delete one or more new indexes whose search parameters are below the threshold.

A fifth aspect of the present application provides a computing device, including a processor, a memory, and a communication interface, wherein the processor is configured to execute the data configuration method provided by the first aspect of the present application by calling program code stored in a memory. .

A sixth aspect of the present application provides a computing device, including a processor, a memory, and a communication interface, wherein the processor is configured to execute the index management method provided by the second aspect of the present application by calling program code stored in a memory. .

The seventh aspect of the present application provides a computer program product, which may be a software installation package, and when the software installation package is executed by the computing device, perform the first aspect or any implementation manner of the first aspect of the present application. The data configuration method provided.

The eighth aspect of the present application provides a computer program product, which may be a software installation package, when the software installation package is executed by the computing device, performing the second aspect or the second aspect of the present application. The index management method provided.

The ninth aspect of the present application provides a storage medium, where the program code is stored, and when the program code is run by the computing device, the data configuration method provided by the first aspect of the present application is executed. The storage medium includes, but is not limited to, a flash memory, a hard disk (English: hard disk drive, HDD), or a solid state drive (English: solid state drive, abbreviated as SSD).

A tenth aspect of the present application provides a storage medium, where the program code is stored, and when the program code is run by the computing device, the index management method provided by the second aspect of the present application is executed. The storage medium includes, but is not limited to, a flash memory, an HDD, or an SSD.

DRAWINGS

Figure 1 (a) is a schematic diagram of an implementation of the search system;

Figure 1 (b) is a schematic diagram of another implementation of the search system;

2 is a structural diagram of an embodiment of a computing device provided by the present application;

FIG. 3 is a flowchart of an embodiment of a data configuration method provided by the present application;

4 is a flowchart of an embodiment of an index management method provided by the present application;

FIG. 5 is a structural diagram of an embodiment of a data configuration apparatus provided by the present application; FIG.

FIG. 6 is a structural diagram of an embodiment of an index management apparatus provided by the present application.

detailed description

The present application provides a data configuration method, an index management method, a related device, and a computing device, which will be separately described below.

The search system is deployed on the search device and interacts with the user through the search device, see Figure 1(a). The search device 100 mainly includes a communication unit 101, a processing unit 102, and a storage unit 103. The storage unit 103 is configured to store data to be saved by the search system, for example, a data file, an index, and the like for storing the search system. The communication unit 101 is configured to search for information interaction between the system and the user, for example, to receive a search request issued by the user, and reply the user with a response message of the search request. The processing unit 102 is configured to perform a data processing operation, for example, for performing a search operation according to a search request of the user, and generating a response message of the search request according to the search result.

Figure 1(a) shows a scenario in which a search system is deployed on a single search device. In practical applications, the search system can also be deployed on multiple search devices, see Figure 1(b). The search system shown in FIG. 1(b) includes a plurality of search devices 100 as shown in FIG. 1(a), and data to be saved by the search system is distributed and stored in a storage unit in each search device 100, each Information exchange between the station search devices 100 through the communication unit 101 is performed. When the user sends a search request to one of the search devices 100, the processing unit of the plurality of search devices 100 may perform a distributed search operation according to the search request of the user, and feed back the search result to generate a response message to the user.

The search device in FIG. 1(a) and FIG. 1(b) can be implemented by the computing device 200 shown in FIG. 2, and its organizational structure includes a processor 201, a memory 202, a communication interface 203, and a bus 204. The processor 201 can be an implementation of the processing unit 102, the memory can be an implementation of the storage unit 103, and the communication interface 203 can be an implementation of the communication unit 101.

The processor 201, the memory 202, and the communication interface 203 can implement communication connection with each other through the bus 204, and can also implement communication by other means such as wireless transmission.

The memory 202 may include a volatile memory (English: volatile memory), such as random-access memory (abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviated: ROM), flash memory (English: flash memory), HDD or SSD; the memory 202 may also include a combination of the above types of memory. While the computing device 200 is running, the memory 202 loads data files, indexes, etc. therein for use by the processor 201. When the technical solution provided by the present application is implemented by software, the program code of the software may be saved in the memory 202 and executed by the processor 201.

The processor 201 can be a central processing unit (English: central processing unit, abbreviation: CPU), or can be an application specific integrated circuit (English: application specific integrated circuits, ASIC), field programmable gate array (English: field-programmable gate Array, abbreviation: FPGA) Such as components with data processing functions to achieve. While the computing device 200 is running, the processor 201 calls the program code in the memory 202 to perform a data processing operation.

The communication interface 203 serves as an interaction interface between the user and the search system, and is used to deliver the search request issued by the user to the processor 201, and deliver the response message generated by the processor 201 to the user.

The search system generally uses doc as the basic unit to store information. After the search system is running, a corresponding default index is created for the saved doc, and the default index records the location information of the doc stored in the search system. The user sends a search request when searching, and the search request includes a search field for requesting the search system to find the doc containing the search field. The search system can obtain the doc containing the search field from the location recorded in the matching default index by looking up the default index that matches the search field. The search system sends the doc back to the user in the response message.

The data in doc is generally saved as a structural form of domain + domain values. Each doc can include a domain and its corresponding domain value, and can also include multiple domains and their corresponding domain values. The domain is used to indicate the type of the corresponding domain value, and the domain value is used to record the specific value of the corresponding domain.

The structure of the doc in the search system is managed by a field configuration (English: schema) configuration file. The schema configuration file is a file in xml format, which is generally stored in the conf directory and is used to define the structure of the doc in the search system. Specifically, the fields in the doc are also defined by the schema configuration file.

For example, the content field is defined in the schema configuration file: the content field is used to indicate the type of "content". If doc 1: ("hostname: node 1, IP: 192.199.0.1") is saved in the search system, doc 1 includes the content field, and the domain value of the content field of doc 1 is "hostname: node 1, IP: 192.199 .0.1”.

For another example, suppose that the schema configuration file defines a hostname field and an IP domain in addition to the content field. The hostname field is used to indicate the type of "hostname", and the IP domain is used to indicate the type of "IP address". If the search system holds doc 2: ("hostname: node 1, IP: 192.199.0.1", "hostname: node 1", "IP: 192.199.0.1"), then doc 2 includes the content domain, hostname domain, and IP. Domain, where the domain value of the content field is "hostname:node 1, IP:192.199.0.1", the domain value of the hostname domain is node 1 (that is, the host name is node 1), and the domain value of the IP domain is 192.199.0.1 ( That is, the IP address is 192.199.0.1).

After the schema configuration file defines the domain, the search system can implement the domain search function. Search by domain is often faster and more efficient than direct search. For example, suppose the user sends a search request to "IP: 192.199.0.1". If the schema configuration file defines an IP domain in addition to the content field, the search system directly searches for a doc including an IP domain and an IP domain with a domain value of 192.199.0.1. If the schema configuration file only defines the content field and no IP domain is defined, the search system needs to search whether the domain value of the content field of each doc includes the "IP:192.199.0.1" field. Obviously, defining multiple domains through the schema configuration file enables the search system to perform domain-by-domain search, which can reduce the number of docs searched and the length of search fields, thereby improving the speed and efficiency of the search operation.

In the current technology, the domain of the schema configuration file is generally set by the technician. The artificially set domain does not necessarily be close to the user's immediate need for the search system, so the speed and efficiency of the domain search cannot be improved.

In order to solve the above problem, the present application provides a data configuration method, and the search device 100 shown in FIG. 1(a) and FIG. 1(b) and the computing device 200 shown in FIG. 2 execute the method at runtime, which is basically See Figure 3 for the process:

301. Receive N search requests sent by a user, where the N search requests include M search fields.

The search system receives N search requests sent by the user, where N is a positive integer greater than 1. The N search request is not specifically limited. For example, the N search requests may be search requests received by the search system within a preset time period. For example, the N search requests may be The latest N search requests sent by the user received by the search system.

Each of the N search requests includes a search field for searching for a doc containing the search field. Wherein, each search request may include one search field, and may also include multiple search fields.

If a search request includes multiple search fields, the multiple search fields may be connected by "AND", "OR" or other logical connection words, and are used to indicate "and", "or", etc., and are not used in this application. limited.

Among the N search requests, the search fields included in different search requests may be the same or different. In the present application, the M search requests include a total of M different search fields as an example, where M is a positive integer.

302. Determine a domain to which the M search fields belong.

The search system determines the domain to which each of the M search fields belongs, that is, determines the type of each of the M search fields.

In some scenarios, the search field may already carry the domain to which it belongs. In this scenario, the search system can directly determine the domain to which the search field belongs based on the search field in the search request. For example: If the search request is "IP: 192.199.0.1", then it is obvious that IP is the domain to which the search field belongs.

In some scenarios, the search field may not carry the domain it belongs to. In this scenario, the search system cannot directly determine the domain to which the search field belongs based on the search field in the search request. However, since the corresponding message of the search request carries the complete doc, and the doc carries the domain, the search system can determine the domain to which the search field belongs according to the response. For example, if the search field sent by the user is only "192.199.0.1", and the corresponding message of the search request carries doc 1: ("hostname: node 1, IP: 192.199.0.1"), it is obvious that IP is the domain to which the search field belongs.

Optionally, the search system may determine the domain to which the search field belongs based on the interval in the search request or response message. For example, if the search request is "IP: 192.199.0.1", the search system can determine that the field IP in front of the interval ":" in the search request is the domain to which the search field belongs. For another example, if the search request is "192.199.0.1" and the response message carries doc 1: ("hostname: node 1, IP: 192.199.0.1"), the search system can determine that the response message is located at 192.199. The field IP preceded by 0.1 adjacent spacer ":" and located after the spacer "," is the domain to which the search field belongs. The search system determines the domain to which the search field belongs according to the format of the doc. This application only uses the intervals ":" and "," as an example. In some search systems, it may also be based on other The spacer is used to determine the domain to which the search field belongs, which is not limited in this application.

303. Determine K hotspot domains.

After the search system determines the domain to which the M search fields belong, select in the domain to which the M search fields belong K hotspots, where K is a positive integer.

Among the M search fields, different search fields may have the same or different domains. Therefore, in the domain to which the M search fields belong, some domains may include multiple search fields, and some domains may include one search field. Optionally, the search system may determine, in the domain to which the M search fields belong, the first K domains including the maximum number of search fields as the hotspot domain.

304. Add the K hotspot domains to the schema configuration file.

After the search system determines the hotspot domain, add the hotspot domain to the schema configuration file.

In the data configuration method provided by the embodiment, the search system receives N search requests sent by the user, and determines a domain to which the M search fields in the N search requests belong, and then in the domain to which the M search fields belong. Determine K hotspot domains and add the K hotspots to the schema configuration file. In this way, after the search system subsequently receives the search field belonging to the hotspot domain, the domain search can be directly performed. In this embodiment, the domain in the schema configuration file is not a domain set by a technician, but is a hotspot domain determined by the search system according to a search request sent by the user immediately. Since the hotspot domain is a domain with a higher search frequency among the N search requests, the hotspot domain has a high probability to be searched again by the user in the subsequent time. By adding a hotspot domain to the schema configuration file, the frequency of searching by domain can be increased, and the speed and efficiency of the domain search can be fully utilized to further improve the search performance of the search system.

It should be noted that, since the schema configuration file is used to define the configuration file in the doc format in the search system, after the hotspot domain is added to the schema configuration file, the search system needs to update the system according to the schema configuration file to which the hotspot domain is added. The saved doc and the default index of the doc. After the doc and its default index update are complete, the search system can perform subsequent search operations.

Optionally, after step 303, the search system may further perform the steps:

305. Determine a domain value format of the K hotspot domains.

After the search system determines that the K hotspot domains are determined, the domain value format of the K hotspot domains is determined according to the search fields included in each of the K hotspot domains. The domain value format of the hotspot domain indicates the format in which the domain value of the hotspot domain conforms.

Specifically, the search system may determine a format in which the search fields included in each hotspot domain conform to each other as the domain value format of each hotspot domain. For example, if the hotspot domain is "IP", the IP domain includes two search fields: "192.199.0.1" and "192.199.0.2". The search system then determines "192.199.0.*" as the domain value format of the IP domain, where * indicates a fuzzy match.

The field value format may be in the form of a regular expression or other forms, which is not limited in this application.

The application does not limit the order of step 305 and step 304, and step 305 may also precede step 304.

Optionally, after determining the domain value format of the K hotspot domains, the search system receives the first search request newly sent by the user, where the first search request includes the first search field. If the first search field does not carry the domain to which it belongs, the search system determines whether the first search field conforms to the format of the hotspot domain. If the first search field conforms to the format of the first domain in the hotspot domain, the first search field is considered to belong to the first domain, and the search system may perform a domain-by-domain search operation.

Optionally, the search system may count the search data corresponding to each domain in the domain defined by the schema configuration file every preset period. The search data includes one or more of the searched times, the searched frequency, and the search hit ratio of the corresponding domain in the current preset period. Search system deletes search data in schema configuration file One or more domains below the threshold to implement dynamic retirement of non-hotspot domains in the schema configuration file.

The data configuration method shown in FIG. 3 achieves performance improvement of the search system by dynamically modifying the schema configuration file according to the user's search request. The following describes an index management method to achieve the same purpose of improving the performance of the search system. The search device 100 shown in FIG. 1(a) and FIG. 1(b) and the computing device 200 shown in FIG. 2 execute the method at runtime. The basic flow is shown in FIG. 4:

401. Receive N search requests sent by the user, where the N search requests include M search fields.

The search system receives N search requests sent by the user, where N is a positive integer. The N search request is not specifically limited. For example, the N search requests may be search requests received by the search system within a preset time period. For example, the N search requests may be The latest N search requests sent by the user received by the search system.

Each of the N search requests includes a search field for searching for a doc containing the search field. Wherein, each search request may include one search field, and may also include multiple search fields. A plurality of search fields in a search request may be connected by "AND", "OR" or other logical connection words, and are used to indicate "and", "or", etc., which are not limited in the present application. Among the N search requests, the search fields included in different search requests may be the same or different. In the present application, the M search requests include a total of M different search fields as an example, where M is a positive integer.

402. Determine L domains to which the M search fields belong.

Optionally, the search system may determine the domain to which the search field belongs based on the interval in the search request or response message. For example, if the search request is "IP: 192.199.0.1", the field IP in front of the interval ":" in the search request is the domain to which the search field belongs. For another example, if the search request is "192.199.0.1" and the response message carries doc 1: ("hostname: node 1, IP: 192.199.0.1"), the response message is located adjacent to 192.199.0.1. The field IP before the separator ":" and located after the spacer "," is the domain to which the search field belongs. The search system determines the domain to which the search field belongs according to the format of the doc. This application only uses the intervals ":" and "," as an example. In some search systems, it may also be based on other The spacer is used to determine the domain to which the search field belongs, which is not limited in this application.

Among the M search fields, different search fields may have the same or different domains. In this embodiment, only the M search fields belong to L different domains as an example for description.

403. Determine a domain value format of the L domains.

The inventor of the present application has found through research that the user's search behavior is local in time: if a user requests to search for a certain search field at a certain time, the search field and the field similar to the search field are in a later period of time. There is a greater probability of being searched again. To this end, in the present embodiment, after determining the L domains to which the M search fields belong, the search system determines the domain value format of each domain according to the search fields included in each of the L domains. It can be considered that fields that conform to the field value format of the L domains have a higher probability of being searched in subsequent runs of the search system.

Specifically, the search system may determine, in a format that the search fields included in each of the L domains are consistently matched, a domain value format of each domain. For example, if there are domains "IP" in the L domains, the IP domain includes two search fields: "192.199.0.1" and "192.199.0.2". The search system then determines "192.199.0.*" as the domain value format of the IP domain, where * indicates a fuzzy match.

404. Determine a first doc that includes a field that conforms to a field value format.

After the search system determines the domain value format of each domain in the L domains, the first doc is determined in the doc saved by the search system, where the first doc is: including the domain value corresponding to any one of the L domains. The doc of the formatted field. It can be understood that the number of the first docs may be one or more.

For example, the search system has determined that the domain value format of the IP domain is "192.199.0.*". Then, since doc 1: ("hostname: node 1, IP: 192.199.0.1") includes the field "192.199.0.1", and "192.199.0.1" conforms to the field value format "192.199.0.*", the doc is 1 times Determined as the first doc.

There are many ways in which the search system determines the first doc. For example, the search system may use the domain value format of the L domains as a search field, and directly search the default index of the search system to obtain the first doc.

405. Generate a second doc.

After the search system determines the first doc, a corresponding second doc is generated according to the field in the first doc that conforms to the field value format. The second doc includes: a field corresponding to the field value format in the corresponding first doc, and a field of the field.

For example, the search system has determined that the domain value format of the IP domain is "192.199.0.*", and the first doc is: ("hostname: node 1, IP: 192.199.0.1"), where the first doc includes fields. "192.199.0.1" conforms to the field value format "192.199.0.*", and the search system generates a corresponding second doc according to the first doc: ("IP: 192.199.0.1").

Since the number of the first docs may be one or more, the number of the second docs may also be one or more. However, since the second doc is generated according to part of the doc (ie, the first doc) in the original doc of the search system, the number of the second doc is much smaller than the number of original docs of the search system; The second doc includes only one field and one field value field, and its length is also smaller than the original doc of most search systems.

406. Create a new index for the second doc.

After the search system generates the second doc, a corresponding new index is created for the second doc.

Since the number and length of the second doc are both small, the data volume of the new index of the second doc is much smaller than the data volume of the default index of the original doc of the search system.

In the index management method provided in this embodiment, the search system receives N search requests sent by the user; determines L domains to which the M search fields belong to the N search requests; and determines a domain value format of the L domains; A first doc containing a field conforming to the field value format is determined in the doc saved by the search system; a second doc is generated according to the first doc; and a new index is established for the second doc. Since the second doc conforms to the domain value format of the L domains, There is a greater probability of being searched for in subsequent runs of the search system. Thus, when the search system receives the newly issued search request from the user, the search field in the search request has a high probability of hitting the new index. Since the data volume of the newly created index is much smaller than the data volume of the default index, searching for the new index can greatly save the workload of the search system and improve the search speed and efficiency of the search system, and improve the search index. Search system search performance.

Optionally, after the step 406, the search system receives the target search request newly sent by the user, where the target search request includes a target search field for requesting to search for a doc including the target search field. The search system searches for a new index that matches the target search field. If a new index matching the target search field is found, the search system obtains the second doc corresponding to the newly created index, and carries the acquired second doc. The response message is fed back to the user. If a new index that matches the target search field is not found, the search system looks for a default index that matches the target search field.

Optionally, when a new doc is imported into the search system, if the new doc includes a field that conforms to the field value format determined in step 403, the search system generates a second doc corresponding to the new doc. The specific method for generating the second doc corresponding to the new doc is similar to step 405, and is not described here. After generating the second doc corresponding to the new doc, the search system creates a new index for the second doc corresponding to the new doc, and generates a default index for the new doc.

Optionally, the search system may count the search parameters of each new index every preset period. The search parameter of each new index includes one or more of the searched times, the searched frequency, and the search hit ratio of the domain corresponding to the new index in the current preset period. The search system deletes one or more new indexes whose search parameters are below the threshold to implement dynamic retirement of non-hotspot indexes in the newly created index.

The above embodiment describes the data configuration method and the index management method provided by the present application, and the apparatus for implementing the above method will be described below.

First, the data configuration device for implementing the data configuration method shown in FIG. 3 is introduced. Referring to FIG. 5, the basic structure of the data configuration device includes:

The information receiving module 501 is configured to receive a plurality of search requests sent by the user, where each of the plurality of search requests includes a search field for requesting to search for a data file that includes the search field.

The domain determining module 502 is configured to determine a domain to which each search field belongs in the search field included in the plurality of search requests.

The hotspot determining module 503 is configured to determine one or more hotspot domains in a domain to which each search field belongs.

The configuration modification module 504 is configured to add the one or more hotspot domains to the schema configuration file, and update the data files in the search system according to the schema configuration file to which the one or more hotspot domains are added.

For a detailed description of the data configuration apparatus shown in FIG. 5, reference may be made to the related description in the data configuration method shown in FIG. 3, and details are not described herein.

In the data configuration apparatus provided in this embodiment, the information receiving module 501 receives a plurality of search requests sent by the user, and the domain determining module 502 determines a domain to which each search field in the search field included in the plurality of search requests belongs. The determining module 503 determines the hotspot domain in the domain to which the search field belongs, and the configuration modification module 504 adds the determined hotspot domain to the schema configuration file. In this way, after the search system subsequently receives the search field belonging to the hotspot domain, the domain search can be directly performed. In this embodiment, the domain in the schema configuration file is not a domain set by a technician, but is a hotspot domain determined by the data configuration device according to a search request sent by the user immediately. Due to The hotspot domain is a domain with a high search frequency among the N search requests, so the hotspot domain has a high probability to be searched again by the user in the subsequent time. By adding a hotspot domain to the schema configuration file, the frequency of searching by domain can be increased, and the speed and efficiency of the domain search can be fully utilized to further improve the search performance of the search system.

Optionally, the domain determining module 502 is specifically configured to: according to each search request, and/or a response message of the search system for each search request, determine, by each search field included in the search field included in the multiple search requests. area.

Optionally, the domain determining module 502 is specifically configured to: determine, according to each search request, and/or a slot in the response message of the search request for each search request, each of the search fields included in the multiple search requests. The domain to which the search field belongs.

Optionally, the hotspot determining module 503 is specifically configured to: determine, in the domain to which each search field belongs, the first one or more domains including the search field to be the hotspot domain.

Optionally, the data configuration apparatus further includes a format determining module 505, configured to determine a domain value format of each hotspot domain according to a search field included in each hotspot domain in the one or more hotspot domains.

Optionally, the format determining module 505 is specifically configured to determine, in a format that the search fields included in each hotspot domain in the one or more hotspot domains are consistently matched, a domain value format of each hotspot domain.

Optionally, the configuration modification module 504 is further configured to: in each preset period, count the search data of each domain in the domain defined by the schema configuration file, where the search data includes a domain defined by the schema configuration file in the current preset period. One or more of the number of searches, the frequency of search, and the search hit rate; delete one or more domains whose search data is below the threshold in the schema configuration file.

The index management apparatus for implementing the index management method shown in FIG. 4 is described below. Referring to FIG. 6, the basic structure of the index management apparatus includes:

The receiving information module 601 is configured to receive a plurality of search requests sent by the user, where each of the plurality of search requests includes a search field, configured to request to find a data file that includes the search field;

a determining domain module 602, configured to determine a domain to which each search field belongs in the search field included in the plurality of search requests;

a determining format module 603, configured to determine a domain value format of each domain in a domain to which each search field belongs according to a search field included in each domain in a domain to which each search field belongs;

a file determining module 604, configured to determine, in the search system, a data file that includes a field corresponding to the field value format determined in the determining format module 603, as the first data file;

a file generating module 605, configured to generate a second data file corresponding to each first data file, where each second data file includes a field corresponding to the field value format included in the corresponding first data file, and the The domain to which the field in the field value format belongs;

The index management module 606 is configured to generate a new index corresponding to each second data file, where the new index includes a storage location of the corresponding second data file in the search system.

For a detailed description of the index management apparatus shown in FIG. 6, reference may be made to the related description in the index management method shown in FIG. 4, and details are not described herein.

In the index management apparatus provided in this embodiment, the receiving information module 601 receives a plurality of search requests sent by the user, and the determining domain module 602 determines a domain to which each search field in the search field included in the plurality of search requests belongs, and determines a format. Module 603 determines the domain value format for these fields, and file determination module 604 will include in the search system The data file of the field conforming to the field value format is determined as the first data file, the file generation module 605 generates the second data file corresponding to the first data file, and the index management module 606 generates a new index of the second data file. When the search system receives the newly issued search request from the user, the search field in the search request has a high probability of hitting the new index. Since the data volume of the newly created index is much smaller than the data volume of the default index, searching for the new index can greatly save the workload of the search system and improve the search speed and efficiency of the search system, and improve the search index. Search system search performance.

Optionally, the determining domain module 602 is specifically configured to: according to each search request, and/or a response message of the search system for each search request, determine, by each search field included in the search field included in the multiple search requests. area.

Optionally, the determining domain module 602 is specifically configured to: determine, according to each search request, and/or a slot in the response message of the search request for each search request, each of the search fields included in the multiple search requests. The domain to which the search field belongs.

Optionally, the determining format module 603 is specifically configured to determine, according to a format that the search fields included in each domain in each domain in which the search field belongs, a domain of each domain in each domain in which the search field belongs. Value format.

Optionally, the receiving information module 601 is further configured to: receive a target search request that is sent by the user, where the target search request includes a target search field, and is used to request to find a data file that includes the target search field.

The index management device further includes a file search module 607, configured to: find a new index corresponding to the target search field; if the new index corresponding to the target search field is found, obtain the target search according to the new index corresponding to the target search field. The data file for the field.

Optionally, the file search module 607 is further configured to: if the new index corresponding to the target search field is not found, look for a default index corresponding to the target search field.

Optionally, the file generating module 605 is further configured to: when the new data file is imported in the search system, if the new data file includes a field that determines the format of the field value determined by the format module 603, the new data is generated. a second data file corresponding to the data file, where the second data file corresponding to the new data file includes: a field in the new data file that conforms to the format of the field value, and a format corresponding to the domain value in the new data file The domain to which the field belongs.

The index management module 606 is further configured to: generate a new index corresponding to the second data file corresponding to the new data file, where the new index corresponding to the second data file corresponding to the new data file includes: the corresponding corresponding to the new data file The location where the two data files are saved in the search system.

Optionally, the index management module 606 is further configured to: collect, according to a preset period, a search parameter of each new index, where the search parameter includes the number of times of searching, the frequency to be searched, and the search frequency of each new index in the current preset period. Search for one or more of the hit ratios; delete one or more new indexes whose search parameters are below the threshold.

In an implementation manner, each module in the embodiments shown in FIG. 5 and FIG. 6 may be a software module, and is stored in the memory 202 of the computing device shown in FIG. 2 in the form of program code. And executed by the processor 201.

In another implementation, the modules in the embodiments shown in FIG. 5 and FIG. 6 may be hardware modules, for example, may be a CPU, a hardware chip, or a combination of a CPU and a hardware chip, as shown in FIG. 2 . The processor 201 of the illustrated computing device performs the methods provided herein.

The present application also provides a computer program product, which may be a software installation package that performs the method illustrated in FIG. 3 or FIG. 4 when executed by the computing device.

Examples of docs, search requests, search fields, and response messages exemplified in the specification of the present application are only used to introduce the technical solutions of the present application by way of example, and do not make actual formats of docs, search requests, search fields, and response messages. Any restrictions. For example, in the specification of the present application, doc1 is: ("hostname: node1, IP: 192.199.0.1"). In practical applications, doc 1 can also be in other formats that match the search system settings. For example, domain and domain values can be separated by ":" spacers, or space separators or other spacers can be used. Separate; data from different domains can be separated by a "," spacer, or by a ";" spacer or other separator.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents of the technical solutions of the embodiments of the present invention.

Claims

A data configuration method, applicable to a search system, the search system includes a plurality of data files, each data file including one or more domains, and domain values corresponding to the one or more domains, wherein the domain a type for indicating a corresponding domain value, where the domain value is used to record a specific value of the corresponding domain, the search system further includes a field configuration schema configuration file, where the schema configuration file is used to define the search system. The domain of the data file, characterized in that the method comprises:

And receiving, by the user, a plurality of search requests, each of the plurality of search requests includes a search field, where each search request is used to request to find a data file that includes the search field;

Determining, in the search field included in the plurality of search requests, a domain to which each search field belongs;

Determining one or more hotspot domains in a domain to which each search field belongs;

Adding the one or more hotspot domains to the schema configuration file and updating data files in the search system according to a schema configuration file to which the one or more hotspot domains are added.
The data configuration method according to claim 1, wherein the determining, by the search field included in the plurality of search requests, the domain to which each search field belongs includes:

Determining, according to each of the search requests, and/or the response message of the search system for each of the search requests, a domain to which each of the search fields included in the plurality of search requests belongs.
The data configuration method according to claim 2, wherein said determining said plurality of search requests according to said each search request, and/or said search system responding to said each search request The fields to which each search field in the included search field belongs include:

Determining, according to each of the search requests, and/or a spacer in the response message of each search request by the search system, a domain to which each search field included in the search field included in the plurality of search requests belongs .
The data configuration method according to any one of claims 1 to 3, wherein the determining one or more hotspot domains in the domain to which each search field belongs includes:

The domain in which each of the search fields belongs, including the previous one or more domains with the largest search field, is determined as the hotspot domain.
The data configuration method according to any one of claims 1 to 4, wherein the determining one or more hotspot domains in the domain to which each search field belongs includes

A field value format of each hotspot domain is determined according to a search field included in each of the one or more hotspot domains.
The data configuration method according to claim 5, wherein the determining the domain value format of each hotspot domain according to the search field included in each of the one or more hotspot domains includes:

The format in which the search fields included in each of the one or more hotspot domains are commonly matched is determined to be a domain value format for searching each hotspot domain.
The data configuration method according to any one of claims 1 to 6, wherein the method further comprises:

Searching, for each preset period, search data of each domain in the domain defined by the schema configuration file, where the search data includes the number of searches of the domain defined by the schema configuration file in the current preset period, One or more of search frequency, search hit rate;

One or more domains whose search data is below a threshold are deleted in the schema configuration file.
An index management method, applicable to a search system, the search system includes a plurality of data files, each data file including one or more domains, and domain values corresponding to the one or more domains, wherein the domain a type for indicating a corresponding domain value, where the domain value is used to record a specific value of the corresponding domain, the search system further includes a default index corresponding to the multiple data files, and each default index includes a corresponding The location of the data file in the search system, the method comprising:

And receiving, by the user, a plurality of search requests, each of the plurality of search requests includes a search field, where each search request is used to request to find a data file that includes the search field;

Determining, in the search field included in the plurality of search requests, a domain to which each search field belongs;

Determining a domain value format of each domain in the domain to which each search field belongs according to a search field included in each domain in the domain to which each search field belongs;

Determining, in the search system, a data file including a field conforming to the field value format as a first data file;

Generating, according to the second data file corresponding to each of the first data files, each of the second data files includes a field corresponding to the domain value format included in the corresponding first data file, and the The domain to which the field in the field value format belongs;

Generating a new index corresponding to each of the second data files, where the new index includes a storage location of the corresponding second data file in the search system.
The index management method according to claim 8, wherein the determining, by the search field included in the plurality of search requests, the domain to which each search field belongs includes:

Determining, according to each of the search requests, and/or the response message of the search system for each of the search requests, a domain to which each of the search fields included in the plurality of search requests belongs.
The index management method according to claim 9, wherein said determining said plurality of search requests according to said each search request, and/or said search system responding to said each search request The fields to which each search field in the included search field belongs include:

Determining, according to each of the search requests, and/or a spacer in the response message of each search request by the search system, a domain to which each search field included in the search field included in the plurality of search requests belongs .
The index management method according to any one of claims 8 to 10, wherein the determining each of the search fields according to a search field included in each domain in the domain to which each search field belongs The domain value format for each domain in the domain to which it belongs includes:

And determining, in a format that the search fields included in each domain in each domain in the domain to which the search field belongs, a domain value format of each domain in the domain to which each search field belongs.
The index management method according to any one of claims 8 to 11, wherein the method further comprises:

Receiving a target search request issued by the user, where the target search request includes a target search field, where the target search request is used to request to find a data file that includes the target search field;

Finding a new index corresponding to the target search field;

If the new index corresponding to the target search field is found, the data file including the target search field is obtained according to the new index corresponding to the target search field.
The index management method according to claim 12, wherein the method further comprises:

If the new index corresponding to the target search field is not found, the default index corresponding to the target search field is searched for.
The index management method according to any one of claims 8 to 13, wherein the method further comprises:

When a new data file is imported in the search system, if the new data file includes a field that conforms to the field value format, a second data file corresponding to the new data file is generated, the new data file The second data file corresponding to the data file includes: a field in the new data file that conforms to the format of the field value, and a field in the new data file that belongs to a field that conforms to the field value format;

Generating a new index corresponding to the second data file corresponding to the new data file, where the new index corresponding to the second data file corresponding to the new data file includes: the second data file corresponding to the new data file is The save location in the search system.
The index management method according to any one of claims 8 to 14, wherein the method further comprises:

Searching, for each preset period, a search parameter of each of the newly created indexes, where the search parameter includes one or more of the searched number, the searched frequency, and the search hit ratio of the new index in the current preset period. item;

Delete one or more new indexes whose search parameters are below the threshold.
A data configuration apparatus, applicable to a search system, the search system includes a plurality of data files, each data file including one or more domains, and domain values corresponding to the one or more domains, wherein the domain a type for indicating a corresponding domain value, where the domain value is used to record a specific value of the corresponding domain, the search system further includes a field configuration schema configuration file, where the schema configuration file is used to define the search system. The domain of the data file, wherein the data configuration device comprises:

The information receiving module is configured to receive a plurality of search requests sent by the user, where each of the plurality of search requests includes a search field, where each search request is used to request to search for data including the search field. file;

a domain determining module, configured to determine a domain to which each search field belongs in the search field included in the plurality of search requests;

a hotspot determining module, configured to determine one or more hotspot domains in a domain to which each search field belongs;

And a configuration modification module, configured to add the one or more hotspot domains to the schema configuration file, and update a data file in the search system according to a schema configuration file to which the one or more hotspot domains are added.
The data configuration apparatus according to claim 16, wherein the domain determining module is specifically configured to:

Determining, according to each of the search requests, and/or the response message of the search system for each of the search requests, a domain to which each of the search fields included in the plurality of search requests belongs.
The data configuration apparatus according to claim 17, wherein the domain determining module is specifically configured to:

Determining, according to each of the search requests, and/or a spacer in the response message of each search request by the search system, a domain to which each search field included in the search field included in the plurality of search requests belongs .
The data configuration apparatus according to any one of claims 16 to 18, wherein the hotspot determining module is specifically configured to:

The domain in which each of the search fields belongs, including the previous one or more domains with the largest search field, is determined as the hotspot domain.
The data configuration apparatus according to any one of claims 16 to 19, wherein the apparatus further comprises:

The format determining module is configured to determine a domain value format of each hotspot domain according to a search field included in each hotspot domain in the one or more hotspot domains.
The data configuration apparatus according to claim 20, wherein the format determining module is specifically configured to:

A format in which the search fields included in each of the one or more hotspot domains are commonly matched is determined as a domain value format of each of the hotspot domains.
The data configuration apparatus according to any one of claims 16 to 21, wherein the configuration modification module is further configured to:

Searching, for each preset period, search data of each domain in the domain defined by the schema configuration file, where the search data includes the number of searches of the domain defined by the schema configuration file in the current preset period, One or more of search frequency, search hit rate;

One or more domains whose search data is below a threshold are deleted in the schema configuration file.
An index management apparatus, applicable to a search system, the search system includes a plurality of data files, each data file including one or more domains, and domain values corresponding to the one or more domains, wherein the domain a type for indicating a corresponding domain value, where the domain value is used to record a specific value of the corresponding domain, the search system further includes a default index corresponding to the multiple data files, and each default index includes a corresponding The location of the data file in the search system, the index management device includes:

The receiving information module is configured to receive a plurality of search requests sent by the user, where each of the plurality of search requests includes a search field, where each search request is used to request to search for data including the search field. file;

Determining a domain module, configured to determine a domain to which each search field belongs in the search field included in the plurality of search requests;

a determining format module, configured to determine a domain value format of each domain in the domain to which each search field belongs according to a search field included in each domain in the domain to which each search field belongs;

a file determining module, configured to determine, in the search system, a data file that includes a field that conforms to the field value format, as a first data file;

a file generating module, configured to generate a second data file corresponding to each of the first data files, where each of the second data files includes a field corresponding to the domain value format included in the corresponding first data file, And the domain to which the field conforming to the domain value format belongs;

An index management module is configured to generate a new index corresponding to each of the second data files, where the new index includes a storage location of the corresponding second data file in the search system.
The index management device according to claim 23, wherein the determining domain module is specifically configured to:

Determining, according to each of the search requests, and/or the response message of the search system for each of the search requests, a domain to which each of the search fields included in the plurality of search requests belongs.
The index management device according to claim 24, wherein the determining domain module is specifically configured to:

Determining, according to each of the search requests, and/or a spacer in the response message of each search request by the search system, a domain to which each search field included in the search field included in the plurality of search requests belongs .
The index management apparatus according to any one of claims 23 to 25, wherein the determining format module is specifically configured to:

And determining, in a format that the search fields included in each domain in each domain in the domain to which the search field belongs, a domain value format of each domain in the domain to which each search field belongs.
The index management device according to any one of claims 23 to 26, wherein:

The receiving information module is further configured to receive a target search request that is sent by a user, where the target search request includes a target search field, where the target search request is used to request to search for a data file that includes the target search field;

The index management apparatus further includes a file search module for:

Finding a new index corresponding to the target search field;

If the new index corresponding to the target search field is found, the data file including the target search field is obtained according to the new index corresponding to the target search field.
The index management device according to claim 27, wherein the file search module is further configured to:

If the new index corresponding to the target search field is not found, the default index corresponding to the target search field is searched for.
The index management apparatus according to any one of claims 23 to 28, wherein the file generating module is further configured to:

When a new data file is imported in the search system, if the new data file includes a field that conforms to the field value format, a second data file corresponding to the new data file is generated, the new data file The second data file corresponding to the data file includes: a field in the new data file that conforms to the format of the field value, and a field in the new data file that belongs to a field that conforms to the field value format;

The index management module is further configured to: generate a new index corresponding to the second data file corresponding to the new data file, where the new index corresponding to the second data file corresponding to the new data file includes: the new The storage location of the second data file corresponding to the data file in the search system.
The index management apparatus according to any one of claims 23 to 29, wherein the index management module is further configured to:

Searching, for each preset period, a search parameter of each of the newly created indexes, where the search parameter includes one or more of the searched number, the searched frequency, and the search hit ratio of the new index in the current preset period. item;

Delete one or more new indexes whose search parameters are below the threshold.
A computing device, comprising a processor, a memory, wherein the processor is configured to execute the data configuration method according to any one of claims 1 to 7 by calling program code stored in a memory.
A computing device, comprising a processor, a memory, wherein the processor is configured to execute the index management method according to any one of claims 8 to 15 by calling program code stored in a memory.