A method for multi-directional configuration of a computer to a full-text search server

Abstract

This invention relates to a multi-directional configuration method for a full-text search server, comprising a data preparation layer, a task publishing module, a user behavior recognition layer, and an index configuration module. By abstracting an interface layer, it achieves rapid construction of indexes, fields, aggregations, and display. To avoid repetitive, complex, and tedious index creation, this solution simplifies the entire operation, allowing users to build their own search engine through personalized page customization.

Description

Technical Field

[0001] This invention relates to the field of computers, and more particularly to a method for multi-directional configuration of a computer to a full-text search server. Background Technology

[0002] The underlying RESTful interface of a full-text search server based on distributed multi-user capabilities has the following advantages:

[0003] 1. Utilize the management interface and configure parameters to allow the system to focus more on the business itself.

[0004] 2. Offers multiple types of word segmenters to meet the needs of different scenarios and achieve high matching accuracy in search results.

[0005] 3. Provide diverse and flexible API interfaces to meet diverse business needs. Summary of the Invention

[0006] In view of this, the present invention provides a method for multi-directional configuration of a computer to a full-text search server to solve or partially solve the above-mentioned problems.

[0007] To achieve the effects of the above technical solutions, the technical solution of the present invention is: a multi-directional configuration method for a computer to a full-text search server, comprising: a data preparation layer, a task publishing module, a user behavior recognition layer, and an index configuration module;

[0008] The user behavior recognition layer includes a permission recognition module and a search application interface. Users log in to the computer's multi-directional configuration method for the full-text search server by entering their username and password using a mouse and keyboard. If the multi-directional configuration method recognizes the username and password as correct, the permission recognition module verifies the user's identity. The permission recognition module supports both account verification and IP address verification, with account verification having higher priority than IP address verification. The permission recognition module first verifies the user account; if it cannot recognize the user account, it then verifies the user's IP address. Users in the multi-directional configuration method are divided into fixed users and random users. Fixed users have the permission to query and modify data, while random users only have the permission to modify data. IP addresses in the multi-directional configuration method are divided into fixed IP addresses and random IP addresses. Fixed user IP addresses are saved as fixed IP addresses, and random user IP addresses are saved as random IP addresses. IP addresses that the permission recognition module cannot recognize have the same permissions as random IP addresses.

[0009] The index configuration module stores parameters for index building; it also includes a custom index interface; this interface configures index parameters, index fields, and field aggregations; index parameters include index name, shards, and replica size; index fields include field type and tokenizer; field aggregations are automatically matched based on field type; and the replica size is modifiable.

[0010] The data preparation layer includes a relational database and a business database. The relational database is used to store the data source of the computer's multi-directional configuration method for the full-text search server, the system configuration information of the computer's multi-directional configuration method for the full-text search server, and the user permission information of the computer's multi-directional configuration method for the full-text search server. The business database is used to store business data, which is the data processed by the task publishing module.

[0011] The metadata aggregation module retrieves valid data from the relational database, preprocesses the valid data, and unifies the format of the preprocessed metadata. The metadata aggregation module then sends the formatted metadata to the direction verification module. Valid data is data that is relevant to the task.

[0012] The direction verification module deletes data from the received, formatted metadata that does not conform to the computer's requirements for multi-directional configuration methods of the full-text search server. The direction verification module then sends the metadata after deleting some data to the storage and exchange module. The timing of the direction verification module sending the metadata after deleting some data to the storage and exchange module must match the storage time of the parameters for data collection and index construction.

[0013] The storage and switching module stores the received metadata after partial data deletion in the main memory; if the storage and switching module receives a signal that the memory capacity in the main memory is insufficient, the storage and switching module will transfer part of the data stored in the main memory to the relay module.

[0014] The storage exchange module has multiple buffers. When the index configuration module builds each index event, the storage exchange module allocates a buffer to it. Users can configure the size of the buffer. The buffer is used to provide data to the task publishing module. The data processing flow of the storage exchange module includes the following steps:

[0015] Step S1: After receiving the metadata after deleting some data, the storage exchange module configures an event sequence number for each index event; the event sequence number indicates the order of the index events within the system, the event sequence number is incremented, and the event sequence number is generated based on the current system's maximum event sequence number; the index events include all indexes established by the computer in the multi-directional configuration method of the full-text search server; the maximum event sequence number is the maximum value of the index event sequence numbers stored in the internal memory and relay module;

[0016] Step S2: The storage exchange module partitions the metadata after partial data deletion. Based on the index configuration parameters, it places the metadata into different attribute partitions and synchronously modifies the secondary number field of the data placed in different attribute partitions. The secondary number field indicates the order of the metadata after partial data deletion within the index event. If multiple index events are configured with the same data, the storage exchange module copies the same data and places the copied data into the corresponding attribute partition. If the metadata after partial data deletion is the last record within a transaction event, the end marker field of the metadata after partial data deletion needs to be set to 1. The end marker field can be 0 or 1. The end marker field indicates whether the metadata after partial data deletion is the last data record within the index event. A value of 0 indicates that the index event has not been completed, and a value of 1 indicates that the index event has been completed.

[0017] Step S3: The task publishing module requests data to be read from the storage and exchange module using the event sequence number;

[0018] Step S4: The storage exchange module queries the size of the requested index event using the event sequence number requested by the task publishing module. If the current cache of the attribute fragment where the requested index event is located is insufficient, the storage exchange module will send a portion of the metadata after deleting some data as the data to be sent to the relay module. After receiving the data, the relay module sends feedback information to the storage exchange module. After receiving the feedback information, the storage exchange module deletes the data. When selecting data to send, the storage exchange module must send all the data of the index event together. The storage exchange module is not allowed to send only a portion of the data of the index event.

[0019] The storage and exchange module periodically maintains the critical sequence number for each buffer, including the maximum and minimum event sequence numbers. The minimum event sequence number is the minimum value of the stored index event sequence number in the relay module. Users request data through the search application interface using either keyword application or index pointer application. In the keyword application interface, the user selects a built index. The index configuration module matches index pointers based on the selected index and sends the matched pointers to the storage and exchange module. The storage and exchange module then queries the buffer corresponding to the received matched index pointer and sends the retrieved data to the index configuration module. Alternatively, in the keyword application interface, the user enters keywords from a built index. The index configuration module matches the index pointer with the highest relevance to the keywords in the built index. If such a pointer exists... If an index pointer is found, the index configuration module sends the index pointer with the highest relevance to the keywords of the built index to the storage exchange module. The storage exchange module matches the event sequence number based on the index pointer with the highest time relevance to the keywords of the built index. If the storage exchange module can find the sequence number corresponding to the index pointer with the highest time relevance to the keywords of the built index, it queries the data based on the matched event sequence number. If the matched event sequence number is greater than or equal to the minimum event sequence number, the storage exchange module sends the matched event sequence number to the relay module to query the data in the buffer corresponding to the matched event sequence number. If the matched event sequence number is less than the minimum event sequence number, the storage exchange module sends the matched event sequence number to the internal memory to query the data in the buffer corresponding to the matched event sequence number. If the matched event sequence number is greater than the maximum event sequence number, the storage exchange module directly returns an input error message. The storage exchange module will then feed back the information returned by the query based on the matched event sequence number to the index configuration module.

[0020] The beneficial results of this invention are as follows: This invention provides a multi-directional configuration method for a computer to a full-text search server, including a data preparation layer, a task publishing module, a user behavior recognition layer, and an index configuration module. By abstracting an interface layer, it achieves rapid construction of indexes, fields, aggregations, and display. To avoid repetitive, complex, and tedious index creation, this solution simplifies the overall operation complexity, allowing users to build their own search engine through personalized page customization. Detailed Implementation

[0021] To make the technical problem to be solved, the technical solution, and the beneficial effects of this invention clearer, the invention will be described in detail below with reference to embodiments. It should be noted that the specific embodiments described herein are only for explaining the invention and are not intended to limit the invention. Products that can achieve the same function are equivalent substitutions and improvements, and are all included within the protection scope of this invention. The specific method is as follows:

[0022] Example 1: This example specifically introduces a common method for configuring a computer to a full-text search server in multiple directions, as follows:

[0023] The multi-directional configuration method for a computer to a full-text search server includes: a data preparation layer, a task publishing module, a user behavior recognition layer, and an index configuration module;

[0024] The user behavior recognition layer includes a permission recognition module and a search application interface. Users log in to the computer's multi-directional configuration method for the full-text search server by entering their username and password using a mouse and keyboard. If the multi-directional configuration method recognizes the username and password as correct, the permission recognition module verifies the user's identity. The permission recognition module supports both account verification and IP address verification, with account verification having higher priority than IP address verification. The permission recognition module first verifies the user account; if it cannot recognize the user account, it then verifies the user's IP address. Users in the multi-directional configuration method are divided into fixed users and random users. Fixed users have the permission to query and modify data, while random users only have the permission to modify data. IP addresses in the multi-directional configuration method are divided into fixed IP addresses and random IP addresses. Fixed user IP addresses are saved as fixed IP addresses, and random user IP addresses are saved as random IP addresses. IP addresses that the permission recognition module cannot recognize have the same permissions as random IP addresses.

[0025] The index configuration module stores parameters for index building; it also includes a custom index interface; this interface configures index parameters, index fields, and field aggregations; index parameters include index name, shards, and replica size; index fields include field type and tokenizer; field aggregations are automatically matched based on field type; and the replica size is modifiable.

[0026] The data preparation layer includes a relational database and a business database. The relational database is used to store the data source of the computer's multi-directional configuration method for the full-text search server, the system configuration information of the computer's multi-directional configuration method for the full-text search server, and the user permission information of the computer's multi-directional configuration method for the full-text search server. The business database is used to store business data, which is the data processed by the task publishing module.

[0027] The metadata aggregation module retrieves valid data from the relational database, preprocesses the valid data, and unifies the format of the preprocessed metadata. The metadata aggregation module then sends the formatted metadata to the direction verification module. Valid data is data that is relevant to the task.

[0028] The direction verification module deletes data from the received, formatted metadata that does not conform to the computer's requirements for multi-directional configuration methods of the full-text search server. The direction verification module then sends the metadata after deleting some data to the storage and exchange module. The timing of the direction verification module sending the metadata after deleting some data to the storage and exchange module must match the storage time of the parameters for data collection and index construction.

[0029] The storage and switching module stores the received metadata after partial data deletion in the main memory; if the storage and switching module receives a signal that the memory capacity in the main memory is insufficient, the storage and switching module will transfer part of the data stored in the main memory to the relay module.

[0030] The storage exchange module has multiple buffers. When the index configuration module builds each index event, the storage exchange module allocates a buffer to it. Users can configure the size of the buffer. The buffer is used to provide data to the task publishing module. The data processing flow of the storage exchange module includes the following steps:

[0031] Step S1: After receiving the metadata after deleting some data, the storage exchange module configures an event sequence number for each index event; the event sequence number indicates the order of the index events within the system, the event sequence number is incremented, and the event sequence number is generated based on the current system's maximum event sequence number; the index events include all indexes established by the computer in the multi-directional configuration method of the full-text search server; the maximum event sequence number is the maximum value of the index event sequence numbers stored in the internal memory and relay module;

[0032] Step S2: The storage exchange module partitions the metadata after partial data deletion. Based on the index configuration parameters, it places the metadata into different attribute partitions and synchronously modifies the secondary number field of the data placed in different attribute partitions. The secondary number field indicates the order of the metadata after partial data deletion within the index event. If multiple index events are configured with the same data, the storage exchange module copies the same data and places the copied data into the corresponding attribute partition. If the metadata after partial data deletion is the last record within a transaction event, the end marker field of the metadata after partial data deletion needs to be set to 1. The end marker field can be 0 or 1. The end marker field indicates whether the metadata after partial data deletion is the last data record within the index event. A value of 0 indicates that the index event has not been completed, and a value of 1 indicates that the index event has been completed.

[0033] Step S3: The task publishing module requests data to be read from the storage and exchange module using the event sequence number;

[0034] Step S4: The storage exchange module queries the size of the requested index event using the event sequence number requested by the task publishing module. If the current cache of the attribute fragment where the requested index event is located is insufficient, the storage exchange module will send a portion of the metadata after deleting some data as the data to be sent to the relay module. After receiving the data, the relay module sends feedback information to the storage exchange module. After receiving the feedback information, the storage exchange module deletes the data. When selecting data to send, the storage exchange module must send all the data of the index event together. The storage exchange module is not allowed to send only a portion of the data of the index event.

[0035] The storage and exchange module periodically maintains the critical sequence number for each buffer, including the maximum and minimum event sequence numbers. The minimum event sequence number is the minimum value of the stored index event sequence number in the relay module. Users request data through the search application interface using either keyword application or index pointer application. In the keyword application interface, the user selects a built index. The index configuration module matches index pointers based on the selected index and sends the matched pointers to the storage and exchange module. The storage and exchange module then queries the buffer corresponding to the received matched index pointer and sends the retrieved data to the index configuration module. Alternatively, in the keyword application interface, the user enters keywords from a built index. The index configuration module matches the index pointer with the highest relevance to the keywords in the built index. If such a pointer exists... If an index pointer is found, the index configuration module sends the index pointer with the highest relevance to the keywords of the built index to the storage exchange module. The storage exchange module matches the event sequence number based on the index pointer with the highest time relevance to the keywords of the built index. If the storage exchange module can find the sequence number corresponding to the index pointer with the highest time relevance to the keywords of the built index, it queries the data based on the matched event sequence number. If the matched event sequence number is greater than or equal to the minimum event sequence number, the storage exchange module sends the matched event sequence number to the relay module to query the data in the buffer corresponding to the matched event sequence number. If the matched event sequence number is less than the minimum event sequence number, the storage exchange module sends the matched event sequence number to the internal memory to query the data in the buffer corresponding to the matched event sequence number. If the matched event sequence number is greater than the maximum event sequence number, the storage exchange module directly returns an input error message. The storage exchange module will then feed back the information returned by the query based on the matched event sequence number to the index configuration module.

[0036] The beneficial results of this invention are as follows: This invention provides a multi-directional configuration method for a computer to a full-text search server, including a data preparation layer, a task publishing module, a user behavior recognition layer, and an index configuration module. By abstracting an interface layer, it achieves rapid construction of indexes, fields, aggregations, and display. To avoid repetitive, complex, and tedious index creation, this solution simplifies the overall operation complexity, allowing users to build their own search engine through personalized page customization.

[0037] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the claims. Furthermore, the above description should be understood and implemented by those skilled in the art; therefore, any equivalent modifications made based on the disclosure of this invention should be included within the scope of these claims.

Claims

1. A method for multi-directional configuration of a computer to a full-text search server, characterized in that, include: Data preparation layer, task publishing module, user behavior recognition layer, index configuration module; The user behavior recognition layer includes a permission recognition module and a search application interface. Users log in to the computer-to-full-text search server multi-directional configuration method by inputting their username and password using a mouse and keyboard. If the multi-directional configuration method recognizes the username and password as correct, the permission recognition module verifies the user's identity. The permission recognition module supports both account verification and IP address verification, with account verification having higher priority than IP address verification. The permission recognition module first verifies the user account; if it cannot recognize the user account, it then verifies the user's IP address. Users in the computer-to-full-text search server multi-directional configuration method are divided into fixed users and random users. Fixed users have the permission to query and modify data, while random users only have the permission to modify data. IP addresses in the computer-to-full-text search server multi-directional configuration method are divided into fixed IP addresses and random IP addresses. The IP address of a fixed user is saved as the fixed IP address, and the IP address of a random user is saved as the random IP address. The permissions of an IP address that the permission recognition module cannot recognize are equivalent to the permissions of the random IP address. The index configuration module is used to store parameters for index construction; the index configuration module has a custom index interface; the custom index interface is used to configure index parameters, index fields, and field aggregations; the index parameters include index name, shards, and replica size; the index fields include field type and tokenizer; the field aggregations are automatically matched according to the field type; the replica size is modifiable; The data preparation layer includes a relational database, a business database, and a metadata aggregation module; The relational database is used to store the data source of the computer's multi-directional configuration method for the full-text search server, the system configuration information of the computer's multi-directional configuration method for the full-text search server, and the user permission information of the computer's multi-directional configuration method for the full-text search server; the business database is used to store business data, which is the data processed by the task publishing module. The metadata aggregation module retrieves valid data from the relational database, preprocesses the valid data, unifies the format of the preprocessed metadata, and sends the format-unified metadata to the direction verification module; the valid data is data that is relevant to the task. The direction verification module deletes data from the received, format-unified metadata that does not conform to the computer's multi-directional configuration method for the full-text search server, and sends the metadata after deleting some data to the storage and exchange module. The time when the direction verification module sends the metadata after deleting some data to the storage exchange module must match the storage time of the parameters for data collection and index construction. The storage exchange module stores the received metadata after the deletion of the data in the internal memory; If the storage exchange module receives a signal that the memory capacity in the internal memory is insufficient, the storage exchange module will transfer a portion of the data stored in the internal memory to the relay module. The storage exchange module has multiple buffers. When the index configuration module constructs each index event, the storage exchange module allocates one of these buffers to the index configuration module. The user can configure the size of the buffer. The buffer is used to provide data to the task publishing module. The data processing flow of the storage exchange module includes the following steps: Step S1: After receiving the metadata after deleting some data, the storage exchange module configures an event sequence number for each index event; the event sequence number indicates the order of the index events within the system, the event sequence number is incremental, and the event sequence number is generated based on the current system's maximum event sequence number; the index events include all indexes established by the computer in the multi-directional configuration method for the full-text search server; the maximum event sequence number is the maximum value of the index event sequence numbers stored in the internal memory and the relay module; Step S2: The storage exchange module partitions the metadata after deleting some data, and places the metadata after deleting some data into different attribute segments according to the index configuration parameters. The secondary number field of the data placed in different attribute segments is modified synchronously. The secondary number field is used to indicate the order of the metadata after deleting some data within the index event. If multiple index events are configured with the same data, the storage exchange module copies the same data and places the copied data into the attribute segment corresponding to the same data. If the metadata after deleting some data is the last data record within a transaction event, then the end marker field of the metadata after deleting some data needs to be set to 1. The end marker field can be 0 or 1. The end marker field indicates whether the metadata after deleting some data is the last data record within an index event. If the end marker field is 0, it means that the index event has not been completed. If the end marker field is 1, it means that the index event has been completed. Step S3: The task publishing module requests to read data from the storage and exchange module using the event sequence number; Step S4: The storage exchange module queries the size of the requested index event using the event sequence number requested by the task publishing module. If the current cache of the attribute fragment where the requested index event is located is insufficient, the storage exchange module downloads a portion of the metadata after deleting some data as the download data and sends it to the relay module. After receiving the download data, the relay module sends feedback information to the storage exchange module. After receiving the feedback information, the storage exchange module deletes the download data. When selecting the download data, the storage exchange module must select all the data of the index event to download together. The storage exchange module is not allowed to select only a portion of the index event data to download. The storage exchange module periodically maintains the important sequence number of each buffer, which includes the cached maximum event sequence number and minimum event sequence number; the minimum event sequence number is the minimum value of the stored index event sequence number in the relay module. Users can request data in the search application interface using either keyword application or index pointer application. In the keyword application interface, users select a built index. The index configuration module then matches an index pointer based on the selected index. The index configuration module sends the matched index pointer to the storage exchange module. The storage exchange module queries the data in the buffer corresponding to the received matched index pointer based on the received matched index pointer. The storage exchange module then sends the queried data in the buffer corresponding to the received matched index pointer back to the index configuration module. The user inputs keywords from the built index into the keyword application interface. The index configuration module matches the keywords with the most relevant index pointers. If an index pointer with the highest relevance exists, the index configuration module sends it to the storage exchange module. The storage exchange module matches the index pointer with the highest time relevance to the keywords with the event sequence number. If the storage exchange module can find a sequence number corresponding to the index pointer with the highest time relevance to the keywords, it then uses the matched event sequence number... If the matched event sequence number is greater than or equal to the minimum event sequence number, the storage exchange module sends the matched event sequence number to the relay module to query the data in the buffer corresponding to the matched event sequence number. If the matched event sequence number is less than the minimum event sequence number, the storage exchange module sends the matched event sequence number to the internal memory to query the data in the buffer corresponding to the matched event sequence number. If the matched event sequence number is greater than the maximum event sequence number, the storage exchange module directly returns an input error message. The storage exchange module will then feed back the information returned by the matched event sequence number query to the index configuration module.