KR102415155B1 - Apparatus and method for retrieving data - Google Patents

Abstract

A data retrieval apparatus and method are disclosed. A data retrieval apparatus according to an embodiment includes: a change history cache module configured to store identification information of a changed data item when a change event for a data item stored in a database occurs; a data retrieval module for receiving a data retrieval request from a user and for receiving a retrieval result according to the data retrieval request by inquiring a search engine; and a filtering module that searches the database for data items corresponding to the identification information stored in the change history cache module, replaces at least a portion of the search results with the searched data items, and provides them to the user.

Description

Data retrieval device and method

Embodiments of the present invention relate to techniques for effectively retrieving data stored in a database.

As one of the means for storing and managing a large amount of data, there is a database management system (DBMS). In general, a relational database (Relational DataBase Management System; RDBMS) is widely used, but recently, various non-relational databases are also actively used. Hereinafter, these various database management systems will be simply abbreviated as a database.

Most databases are optimized for the basic data processing functions Create, Read, Update, and Delete, but are relatively weak in data retrieval. Accordingly, in many cases, a search engine separate from the database is introduced to supplement the weak search function of the database.

Republic of Korea Patent Publication No. 10-2015-0075407 (2015. 07. 03)

The disclosed embodiments are for improving user convenience and reducing unnecessary server load in an environment in which a database and a search engine synchronized with the database are simultaneously operated.

According to an exemplary embodiment, there is provided a system for retrieving data using a database and a search engine synchronized with the database, wherein when a change event for a data item stored in the database occurs, identification information of the changed data item is obtained, a change history cache module for retrieving and storing data items corresponding to the obtained identification information in the database; a data retrieval module for receiving a data retrieval request from a user and for receiving a retrieval result according to the data retrieval request by inquiring the search engine; and a filtering module that merges the search results and the data items stored in the change history cache module and provides them to the user.

The change event may include one or more of creation, change, and deletion of one or more data items.

The change history cache module may delete a pre-stored data item every preset deletion period.

The filtering module is configured to, when the modification time of the data item stored in the change history cache module is after the modification time of the data item included in the search result, the data item included in the search result to the data stored in the change history cache module items can be replaced.

The filtering module may determine that the corresponding data item has been deleted when the data item corresponding to the obtained identification information does not exist in the database.

The filtering module may receive an additional search result corresponding to the number of deleted data items from the search engine, and reconstruct the search result by using the received additional search result.

According to another exemplary embodiment, there is provided a method for searching data using a database and a search engine synchronized with the database, comprising: obtaining identification information of a changed data item when a change event for a data item stored in the database occurs step; retrieving and storing a data item corresponding to the obtained identification information in the database; receiving a data search request from a user, and receiving a search result according to the data search request by inquiring the search engine; and merging the search result and data items stored by searching in the database and providing them to the user.

The change event may include one or more of creation, change, and deletion of one or more data items.

The storing of the identification information may further include deleting a pre-stored data item at each preset deletion cycle.

The providing may include replacing a data item included in the search result with the inquired and stored data item when the modification time of the inquired and stored data item is after the modification time of the data item included in the search result. can be

The providing, the storing, may be configured to determine that the corresponding data item is deleted when the data item corresponding to the obtained identification information does not exist in the database.

The providing may include: receiving additional search results corresponding to the number of deleted data items from the search engine; and reconstructing the search result by using the received additional search result.

According to the disclosed embodiments, in an environment in which a database and a search engine synchronized with the database are simultaneously operated, user inconvenience due to a time difference between data update between the database and the search engine can be reduced.

In addition, according to the disclosed embodiments, since the data created, modified, or deleted by the user is immediately reflected in the search result, the user is prevented from repeatedly refreshing the search data in order to obtain the updated data. As this can be prevented, unnecessary server load can be reduced.

1 is a block diagram illustrating a data management system according to an embodiment of the present invention;
2 is an exemplary diagram for explaining a process of creating, updating, and deleting data in a data management system according to an embodiment of the present invention;
3 is an exemplary diagram for explaining a process of searching for data in a data management system according to an embodiment of the present invention;
4 is an exemplary diagram for explaining an example in which data discrepancy occurs between a database and a search engine in the process of creating, updating, and deleting data in the data management system according to an embodiment of the present invention;
FIG. 5 is an exemplary diagram for explaining a case in which data is inquired from the terminal in a state where data mismatch between the database and the search engine occurs as shown in FIG. 4
6 is a block diagram illustrating a data search apparatus according to an embodiment of the present invention;
7 is an exemplary diagram for explaining a data search process in a data search apparatus according to an embodiment of the present invention.
8 is a flowchart illustrating a data search method according to an embodiment;

Hereinafter, specific embodiments of the present invention will be described with reference to the drawings. The following detailed description is provided to provide a comprehensive understanding of the methods, devices, and/or systems described herein. However, this is merely an example, and the present invention is not limited thereto.

In describing the embodiments of the present invention, if it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. And, the terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification. The terminology used in the detailed description is for the purpose of describing embodiments of the present invention only, and should in no way be limiting. Unless explicitly used otherwise, expressions in the singular include the meaning of the plural. In this description, expressions such as “comprising” or “comprising” are intended to indicate certain features, numbers, steps, acts, elements, some or a combination thereof, one or more other than those described. It should not be construed to exclude the presence or possibility of other features, numbers, steps, acts, elements, or any part or combination thereof.

1 is a block diagram illustrating a data management system 100 according to an embodiment of the present invention. As shown, the data management system 100 according to an embodiment of the present invention includes a terminal 102 , a service server 104 , a database 106 , and a search engine 108 .

The terminal 102 is a computing device used by the user 110 using the online service to receive the online service. In the disclosed embodiments, the terminal 102 may include a personal computing device such as a desktop computer and a laptop computer, a smart phone, a tablet, a wearable device, and the like.

The service server 104 is a server for providing an online service to the terminal 102 . In one embodiment, the service server 104 provides a service for creating, modifying, or deleting data in the database 106 and the search engine 108 according to the request of the terminal 102, or for inquiring pre-stored data can do.

The database 106 stores and manages data in association with the service server 104 . In the disclosed embodiments, the database 106 is used to encompass various types of database management systems (DBMSs) for storing and managing large amounts of data.

The search engine 108 stores and manages the same data as the database 106 , and provides search results in response to a search request of the service server 104 . As described above, most of the databases 106 are optimized for the basic data processing functions Create, Read, Update, and Delete, but are relatively weak in data retrieval. Accordingly, in many cases, a search engine 108 separate from the database 106 is introduced to supplement the weak search function of the database.

The search engine 108 may retrieve data much more efficiently than the database 106 . The reason is that the database 106 stores data as it is without additional processing, whereas the search engine 108 indexes and stores the data. However, since the indexing process consumes a lot of computing resources in some cases, the search engine 108 takes more time to create, update, and delete data than the database 106 .

Meanwhile, the terminal 102 , the service server 104 , the database 106 , and the search engine 108 may transmit and receive data to and from each other through the communication network 110 . In some embodiments, communication network 110 is the Internet, one or more local area networks, wire area networks, cellular networks, mobile networks, other types of networks, or such networks. may include combinations of these.

2 is an exemplary diagram for explaining a process of creating, updating, and deleting data in the data management system 100 according to an embodiment of the present invention.

First, the terminal 102 requests the service server 104 to change a specific data item. In the present specification, 'change' of a data item is used to indicate any one of creation, update, or deletion of a corresponding data item.

The service server 104 that has received the change request transmits the received change request to the database 106 and the search engine 108 . In this case, in the case of the search engine 108, a separate processing queue 202 (Processing Queue) may be provided in consideration of stability and the like. In this case, the corresponding change request is input to the processing queue 202 , and the search engine 108 sequentially processes the data change request input to the processing queue 202 .

3 is an exemplary diagram for explaining a process of searching for data in the data management system 100 according to an embodiment of the present invention. First, the terminal 102 requests the service server 104 to search for a specific data item. The service server 104 then forwards the received search request to the search engine 108 . As can be seen from FIG. 2 , data changes are reflected in both the database 106 and the search engine 108 , so that the data stored in the database 106 and the search engine 108 maintain a synchronized state. Accordingly, the service server 104 may perform a data search using the search engine 108 optimized for search and provide the search result to the terminal 102 .

In this way, data changes are reflected in both the database 106 and the search engine 108, so that the data stored in the database 106 and the search engine 108 maintain a synchronized state. However, as described above, since the search engine 108 undergoes an indexing process when data is changed, it takes a relatively long time to change data compared to the database 106 . Moreover, when a separate processing queue 202 is provided at the front end of the search engine 108, the time difference between the two becomes wider. Due to such a time difference, there may be cases in which data changes already reflected in the database 106 are not yet reflected in the search engine 108. In this case, the search results of the search engine 108 are stored in the database 106. may vary with This will be described by way of example as shown in FIGS. 4 and 5 .

4 is an example for explaining an example in which data discrepancy occurs between the database 106 and the search engine 108 in the process of creating, updating, and deleting data in the data management system 100 according to an embodiment of the present invention. It is also

First, the terminal 102 requests the service server 104 to change a specific data item. In the illustrated example, an example in which the terminal 102 transmits a request to change A to A' and B to B' and delete C to the service server 104 among the data items stored in the database is shown.

The service server 104 that has received the request forwards the received change request to the database 106 and the search engine 108 . Since the database 106 can immediately process data changes without a separate indexing process, among the data items stored in the database 106, A is changed to A', B is changed to B', and C is deleted. On the other hand, since the change request transmitted to the search engine 108 is still waiting in the processing queue 202 , A, B, and C are still stored in the search engine 108 .

FIG. 5 is an exemplary diagram for explaining a case of inquiring (searching) data to the terminal 102 in a state where data mismatch occurs between the database 106 and the search engine 108 as shown in FIG. 4 . As described above, the data change is still not reflected in the search engine 108 . Therefore, even after the terminal 102 has already transmitted the data change request, the search engine 108 returns the result values A, B, and C before the change according to the data inquiry request of the terminal 102 .

In this case, the user of the terminal 102 feels inconvenient in using the service, such as judging that his/her data change request has not been properly performed or that the performance of the service itself is slow, and thus suspects the quality of the service. In addition, when the user attempts to change data again or continuously refreshes the screen to retrieve the changed data, unnecessary server requests may occur, which may cause a load on the entire system.

6 is a block diagram illustrating a data search apparatus 600 according to an embodiment of the present invention. The data search apparatus 600 according to an embodiment of the present invention operates due to the data change time difference between the database 106 and the search engine 108 in an environment in which the database 106 and the search engine 108 synchronized with the database 106 are simultaneously operated. This is to solve the user's inconvenience and reduce unnecessary server load.

In an embodiment, the data retrieval apparatus 600 may be provided inside the terminal 102 . In this case, the data search apparatus 600 may receive a data search request from an application in the terminal 102 and provide a search result corresponding to the search request to the application. The application may be, for example, a web browser provided in the terminal 102 or a dedicated application for providing a service to the user of the terminal 102 in connection with the service server 104 . In another embodiment, the data retrieval device 600 may be provided inside the service server 104 . In this case, the data search apparatus 600 may receive a data search request from the terminal 102 through the communication network 110 , and provide a search result corresponding to the search request to the terminal 102 .

As shown in FIG. 6 , the data retrieval apparatus 600 according to an embodiment of the present invention includes a change history cache module 602 , a data retrieval module 604 , and a filtering module 606 .

When a change event occurs for a data item stored in the database 106, the change history cache module 602 obtains identification information of the changed data item, and retrieves and stores the data item corresponding to the obtained identification information from the database. do. In one embodiment, the change event may include one or more of creation, change, and deletion of one or more data items.

For example, when a user of the terminal 102 creates a new data item in the database 106 through an application in the terminal 102 or changes (updates) or deletes a previously stored data item, the change history cache module 602 may obtain identification information for identifying the data item to be created, changed, or deleted. In this case, the change history cache module 602 may obtain the identification information from the request to create, change, or delete the data item. Thereafter, the change history cache module 602 may inquire the database 106 using the obtained identification information and store the changed data item.

In one embodiment, when the data item corresponding to the identification information does not exist in the database 106 , the change history cache module 602 determines that the data item has been deleted by the user and replaces the data item with the corresponding data item. You can keep a record of the deletion of the item.

In an embodiment, the change history cache module 602 may delete a pre-stored data item every preset deletion period. The deletion period may be determined in consideration of the time required for the search engine 108 to reflect the data change. As mentioned earlier, the search engine 108 takes longer to change data compared to the database 106 . Accordingly, the change history cache module 602 may be configured to store the changed data item in the database 106 and delete the pre-stored information when sufficient time has elapsed for the search engine 108 to complete the data change. .

The data retrieval module 604 receives a data retrieval request from the user of the terminal 102 , and queries the search engine 108 to receive a search result according to the data retrieval request.

The filtering module 606 inquires the data item stored in the change history cache module 602, and merges the search result of the data retrieval module 604 and the data item stored in the change history cache module 602 to provide the user with the search result. to provide.

In one embodiment, the filtering module 606 queries the data item included in the search result when the modification time of the data item stored in the change history cache module 602 is after the modification time of the data item included in the search result. The above merging process can be performed by replacing the data item with the old data item.

Also, in an embodiment, when the data item corresponding to the identification information is recorded in the change history cache module 602 as being deleted, the filtering module 606 deletes the data item corresponding to the identification information from the search result. can In this case, the filtering module 606 may perform additional searches as many as the number of deleted data items using the search engine 108 , and supplement the existing search results using the additional search results.

In one embodiment, the change history cache module 602 , the data retrieval module 604 , and the filtering module 606 may be implemented on a computing device including one or more processors and a computer-readable recording medium coupled to the processors. The computer-readable recording medium may be internal or external to the processor, and may be connected to the processor by various well-known means. A processor within the computing device may cause each computing device to operate in accordance with the exemplary embodiments described herein. For example, the processor may execute instructions stored in a computer-readable recording medium, and the instructions stored in the computer-readable recording medium, when executed by the processor, cause the computing device to operate according to the exemplary embodiments described herein. can be configured to perform

7 is an exemplary diagram for explaining a data search process in the data search apparatus 600 according to an embodiment of the present invention. In the illustrated embodiment, an example of inquiring data through the data search device 600 in the browser 702 installed in the terminal 102 is shown.

First, it is assumed that, in the browser in the terminal 102 , A is changed to A' and B is changed to B' among the data items stored in the database 106 , and C is deleted. Also, it is assumed that the data change history has already been reflected in the database 106 but has not yet been reflected in the search engine 108 .

In this case, the data items stored in the database 106 are as follows.

A', B', (delete), D, E, F

Also, the data items stored in the search engine 108 are as follows.

A, B, C, D, E, F

Meanwhile, the change history cache module 602 of the data retrieval device 600 inquires the recent data change history in the database 106 and stores the changed data item as follows.

Item A's ID: A'

Item B's ID: B'

Item C's ID: (Deleted)

In such a situation, it is assumed that a search request for inquiring the first five data items among the data items stored in the database 106 is received from the browser 702 to the data search device 600 .

The data retrieval module 604 receiving the retrieval request transmits the retrieval request to a search engine. As described above, since the change history is not yet reflected in the search engine 108, the search engine 108 returns the data item before the change as a search result as follows.

A, B, C, D, E

Meanwhile, the filtering module 606 merges the data item stored in the change history cache module 602 and the search result of the search engine 108 . Specifically, the filtering module 606 reflects the data items stored in the change history cache module 602 and replaces A with A' and B with B' in the search results of the search engine 108, respectively. In addition, the value corresponding to item C is recorded as being deleted in the change history cache module 602, and the filtering module 606 deletes it from the search result. As a result of the deletion, the search result lacks one data item, and in order to supplement this, the filtering module 606 transmits an additional search request to the search engine 108, and receives F as an additional data item in response to this. This is reflected in the search results.

The final search result delivered to the browser 702 through the above process is as follows.

A', B', D, E, F

8 is a flowchart illustrating a data search method 800 according to an embodiment. The method shown in FIG. 8 may be performed, for example, by the above-described data retrieval apparatus 600 . In the illustrated flowchart, the method is described by dividing the method into a plurality of steps, but at least some of the steps are performed in a different order, are performed in combination with other steps, are omitted, are performed in separate steps, or are not shown. One or more steps may be added and performed.

In step 802 , the change history cache module 602 of the data retrieval device 600 obtains identification information of the changed data item when a change event for the data item stored in the database 106 occurs.

In step 804, the change history cache module 602 searches the database for a data item corresponding to the identification information obtained in step 802 and stores it. In this case, when the data item corresponding to the obtained identification information does not exist in the database, the change history cache module 602 may determine that the corresponding data item has been deleted. Also, as described above, the data item stored in the change history cache module 602 may be deleted at every preset deletion period.

In step 806, the data retrieval module 604 of the data retrieval device 600 receives a data retrieval request from a user. In an embodiment, the data retrieval request may be received from an application provided in the terminal 102 .

In step 808, the data retrieval module 604 inquires the retrieval engine 108 to receive a retrieval result according to the data retrieval request.

In step 810, the filtering module 606 merges the search result received from the search engine 108 in step 808 with the data item stored in the change history cache module 602 in step 804 and provides it to the user. In one embodiment, the filtering module 606 is configured to, when the modification time of the data item queried in the database 106 is after the modification time of the data item included in the search result, the data item included in the search result is returned to the queried data item. By replacing with , the merge can be performed.

Further, the filtering module 606 may be configured to, when there is a data item recorded as being deleted in the change history cache module 602 , delete the corresponding data item from the search results. In this case, the filtering module 606 may receive additional search results corresponding to the number of deleted data items from the search engine 108 , and reconstruct the search results using the received additional search results.

Meanwhile, an embodiment of the present invention may include a program for performing the methods described in this specification on a computer, and a computer-readable recording medium including the program. The computer-readable recording medium may include program instructions, local data files, local data structures, etc. alone or in combination. The media may be specially designed and configured for the present invention, or may be commonly used in the field of computer software. Examples of computer-readable recording media include hard disks, magnetic media such as floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and program instructions specially configured to store and execute program instructions such as ROMs, RAMs, flash memories, etc. Hardware devices are included. Examples of the program may include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like.

Although representative embodiments of the present invention have been described in detail above, those of ordinary skill in the art to which the present invention pertains will understand that various modifications are possible without departing from the scope of the present invention with respect to the above-described embodiments. . Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the claims described below as well as the claims and equivalents.

600: data retrieval device
602: Change History Cache Module
604: data retrieval module
606: filtering module

Claims (12)

A system for retrieving data using a database and a search engine that stores data synchronized with the data in the database, the system comprising:
a change history cache module for obtaining identification information of the changed data item when a change event for the data item stored in the database occurs, and retrieving and storing the data item corresponding to the obtained identification information from the database;
a data retrieval module for receiving a data retrieval request from a user and for receiving a retrieval result according to the data retrieval request by inquiring the search engine; and
and a filtering module for merging the search results and the data items stored in the change history cache module and providing them to the user.
The method according to claim 1,
The change event comprises one or more of creation, change, and deletion of one or more data items.
The method according to claim 1,
The change history cache module is configured to delete a pre-stored data item every preset deletion period.
The method according to claim 1,
The filtering module is configured to convert the data item included in the search result to the data stored in the change history cache module when the modification time of the data item stored in the change history cache module is after the modification time of the data item included in the search result. A data retrieval device that replaces an item.
5. The method according to claim 4,
The filtering module is configured to determine that the corresponding data item is deleted when the data item corresponding to the obtained identification information does not exist in the database.
6. The method of claim 5,
The filtering module receives additional search results corresponding to the number of data items deleted from the search engine,
and reconstructing the search result by using the received additional search result.
A method for retrieving data using a database and a search engine that stores data synchronized with data in the database, the method comprising:
obtaining identification information of the changed data item when a change event for the data item stored in the database occurs;
retrieving and storing a data item corresponding to the obtained identification information in the database;
receiving a data search request from a user, and receiving a search result according to the data search request by inquiring the search engine; and
and merging the search results and data items stored by searching in the database and providing them to the user.
8. The method of claim 7,
wherein the change event comprises one or more of creation, change, and deletion of one or more data items.
8. The method of claim 7,
Storing the identification information includes:
The data retrieval method further comprising the step of deleting a pre-stored data item at every preset deletion cycle.
8. The method of claim 7,
The providing step is
and replace the data item included in the search result with the inquired stored data item when the modification time of the inquired and stored data item is after the modification time of the data item included in the search result.
11. The method of claim 10,
The storing is configured to determine that the data item is deleted when the data item corresponding to the obtained identification information does not exist in the database.
12. The method of claim 11,
The providing step is
receiving additional search results corresponding to the number of deleted data items from the search engine; and
and reconstructing the search result by using the received additional search result.

Images