Caching name-based filters in a full-text search engine

• US 8,612,467 B2
• Filed: 02/28/2008
• Issued: 12/17/2013
• Est. Priority Date: 02/28/2008
• Status: Expired due to Fees

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Bernard, Emmanuel
• Primary Examiner(s): Mahmoudi, Tony
• Assistant Examiner(s): PHAN, TUANKHANH D
• Application Number:
  US12/074,042
• Publication Number:
  US 20090222465A1
• Time in Patent Office: 2,119 Days
• Field of Search: 707705-780, 709246-247, 719/340, 719/369
• US Class Current: 707/760
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/335 Filtering based on additional data, e.g. user or group profiles filtering in web context G06F16/9535, G06F16/9536

Abstract

Techniques for filtering a full-text search result in a full-text search engine level are described herein. According to one embodiment, in response to a search query received at an ORM system for a full-text search in a relational database, a full-text search engine is invoked to perform the requested full-text search based on the search query. A filter is utilized to filter a search result generated from the full-text search engine using a filter object representing a filter associated with the search query and returning the filtered result to the application client. Thereafter, the filter object is cached in a cache memory of the ORM system such that the cached filter object can be used in subsequent search queries without having to recreating the same filter object. Other methods and apparatuses are also described.

Claims

1. A computer-implemented method comprising:

receiving, by an object-relational mapping (ORM) system that is executed by a processing system, a search query object for a full-text search in a relational database from an application client, wherein the search query object is in a first format that is incompatible with the relational database being searched;

mapping, by the ORM system, the search query object to a second format that is compatible with the relational database;

invoking, by the ORM system, a full-text search engine to perform the full-text search in view of the mapped search query object;

creating the filter object in response to determining that a filter object associated with the search query object has not been cached within a cache memory of the ORM system;

filtering a search result generated from the full-text search engine using the created filter object and returning the filtered search result to the application client;

caching the filter object in the cache memory of the ORM system such that the cached filter object can be used to filter a subsequent search result in response to receiving a subsequent search query object without having to recreate the filter object;

receiving, by the ORM system, the subsequent search query object for a subsequent full-text search in the relational database from the application client, wherein the subsequent search query object is in the first format that is incompatible with the relational database being searched;

mapping, by the ORM system, the subsequent search query object to the second format that is compatible with the relational database;

invoking, by the ORM system, the full-text search engine to perform the subsequent full-text search in view of the mapped subsequent search query object;

in response to determining that the filter object has been cached within the cache memory of the ORM system, retrieving the cached filter object from the cache memory of the ORM system;

filtering the subsequent search result generated from the full-text search engine using the retrieved filter object and returning the filtered subsequent search result to the application client.

2. The method of claim 1, further comprising defining a filter represented by the filter object, wherein the filter comprises an indication that caching is enabled for the filter object, and wherein caching the filter object is in response to determining that caching is enabled for the filter object.

3. The method of claim 2, wherein defining the filter comprises:

declaring the filter using a filter name in a declaration section; and

associating the filter name with a filter factory that is used to create and implement a functionality of the filter, wherein the filter factory is invoked by referencing the filter name of the filter.

4. The method of claim 3, wherein the filter is one of a plurality of filters associated with the search query object, wherein any one of the plurality of filters can be enabled or disabled by referencing a respective filter name of a respective filter.

5. The method of claim 4, further comprising in response to an update event from an indexing engine associated with the full-text search engine that an index associated with an underlying database has been changed, recaching the filter object in the cache memory of the ORM system to reflect the changed index.

6. The method of claim 5, further comprising in response to a request to set a parameter of the filter identified by the filter name, invoking the filter factory associated with the filter name to configure the parameter of the filter.

7. A non-transitory computer readable medium including instructions that, when executed by a processing system, cause the processing system to perform operations comprising:

receiving, by an object-relational mapping (ORM) system that is executed by the processing system, a search query object for a full-text search in a relational database from an application client, wherein the search query object is in a first format that is incompatible with the relational database being searched;

mapping, by the ORM system, the search query object to a second format that is compatible with the relational database;

invoking, by the ORM system, a full-text search engine to perform the full-text search in view of the mapped search query object;

creating the filter object in response to determining that a filter object associated with the search query object has not been cached within a cache memory of the ORM system;

filtering a search result generated from the full-text search engine using the created filter object and returning the filtered search result to the application client;

caching the filter object in the cache memory of the ORM system such that the cached filter object can be used to filter a subsequent search result in response to receiving a subsequent search query object without having to recreate the filter object;

receiving, by the ORM system, the subsequent search query object for a subsequent full-text search in the relational database from the application client, wherein the subsequent search query object is in the first format that is incompatible with the relational database being searched;

mapping, by the ORM system, the subsequent search query object to the second format that is compatible with the relational database;

invoking, by the ORM system, the full-text search engine to perform the subsequent full-text search in view of the mapped subsequent search query object;

in response to determining that the filter object has been cached within the cache memory of the ORM system, retrieving the cached filter object from the cache memory of the ORM system;

filtering the subsequent search result generated from the full-text search engine using the retrieved filter object and returning the filtered subsequent search result to the application client.

8. The non-transitory computer readable medium of claim 7, wherein the operations further comprise defining a filter represented by the filter object, wherein the filter comprises an indication that caching is enabled for the filter object, and wherein caching the filter object is in response to determining that caching is enabled for the filter object.

9. The non-transitory computer readable medium of claim 8, wherein defining the filter comprises:

declaring the filter using a filter name in a declaration section; and

associating the filter name with a filter factory that is used to create and implement a functionality of the filter, wherein the filter factory is invoked by referencing the filter name of the filter.

10. The non-transitory computer readable medium of claim 9, wherein the filter is one of a plurality of filters associated with the search query object, wherein any one of the plurality of filters can be enabled or disabled by referencing a respective filter name of a respective filter.

11. The non-transitory computer readable medium of claim 10, wherein the operations further comprise in response to an update event from an indexing engine associated with the full-text search engine that an index associated with an underlying database has been changed, recaching the filter object the cache memory of the ORM system to reflect the changed index.

12. The non-transitory computer readable medium of claim 11, wherein the operations further comprise in response to a request to set a parameter of the filter identified by the filter name, invoking the filter factory associated with the filter name to configure the parameter of the filter.

13. An object-relational mapping (ORM) system comprising:

a cache memory to store a filter object associated with a search query object; and

a processing system coupled to the cache memory to;

receive the search query object for a full-text search in a relational database from an application client, wherein the search query object is in a first format that is incompatible with the relational database being searched;

map the search query object to a second format that is compatible with the relational database;

invoke a full-text search engine to perform the full-text search in view of the mapped search query object;

create the filter object in response to a determination that the filter object has not been cached within the cache memory of the ORM system;

filter a search result generated from the full-text search engine using the created filter object and to return the filtered search result to the application client;

cache the filter object in the cache memory of the ORM system such that the cached filter object can be used to filter a subsequent search result in response to receipt of a subsequent search query object without having to recreate the filter object;

receive the subsequent search query object for a subsequent full-text search in the relational database from the application client, wherein the subsequent search query object is in the first format that is incompatible with the relational database being searched;

map the subsequent search query object to the second format that is compatible with the relational database;

invoke the full-text search engine to perform the subsequent full-text search in view of the mapped subsequent search query object;

in response to a determination that the filter object has been cached within the cache memory of the ORM system, retrieve the cached filter object from the cache memory of the ORM system; and

filter the subsequent search result generated from the full-text search engine using the retrieved filter object and return the filtered subsequent search result to the application client.

14. The system of claim 13, wherein the processing system is further to define a filter represented by the filter object, wherein the filter comprises an indication that caching is enabled for the filter object, and wherein caching the filter object is in response to a determination that caching is enabled for the filter object.

15. The system of claim 14, further comprising a filter factory, wherein the processing system is further to declare the filter using a filter name in a declaration section and to associate the filter name with the filter factory that is used to create and implement a functionality of the filter, and wherein the filter factory is invoked by referencing the filter name of the filter.

16. The system of claim 15, wherein the filter is one of a plurality of filters associated with the search query object, wherein any one of the plurality of filters can be enabled or disabled by referencing a respective filter name of a respective filter.

17. The system of claim 16, wherein the processing system is further to, in response to an update event from an indexing engine associated with the full-text search engine that an index associated with an underlying database has been changed, recache the filter object in the cache memory of the ORM system to reflect the changed index.