Relational Query Translation Layer for Search Engines
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Full text search engines do not support relational database type queries, such as join operations or merging metadata field values from different document types, limiting their ability to provide information in manners supported by relational database management systems.
Innovation Solution
A system translates relational database type queries into queries understandable by a full text search engine using a JDBC driver, enabling the search engine to emulate relational database management system functionality and return results in a standard relational database query format.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If full text search engines are used to manage information, then search capabilities are provided, but relational database type queries (join operations, merging metadata field values) are not supported
Solution Approach 1:
A translation layer is introduced between the relational database query interface and the full text search engine. This intermediary component translates SQL queries into search engine-specific query languages, enabling relational database type queries to be executed against the search engine without requiring direct integration or modification of the search engine itself.
Solution Approach 2:
The system provides a universal interface that allows the full text search engine to accept multiple types of queries including both traditional search queries and relational database type queries. The translation layer enables the search engine to handle diverse query formats through a unified architecture.
2Ease of operation
If full text search engines focus on providing lists of individual documents, then simple search functionality is achieved, but access to information in manners supported by relational database management systems is not provided
Solution Approach 1:
The system transforms the query parameters and result formats to bridge between the simple search interface model and the relational database model. By changing how queries are structured and how results are returned, the system enables relational operations like joins and metadata merging while maintaining compatibility with the search engine's core functionality.
3Adaptability or versatility
If attempts are made to enable relational database type queries by integrating full text search capabilities into a relational database, then query functionality is improved, but system complexity and integration requirements increase
Solution Approach 1:
Instead of integrating the search engine into the relational database (as previously attempted), the approach is inverted: the relational database query interface is brought to the search engine through a translation layer. This allows relational queries to be executed against the search engine without requiring the search engine to be embedded within the database system.
Data Source
AI summary
According to one embodiment of the present invention, a system searches content managed by a search engine. The system receives a relational database type query, translates the relational database type query into a query for the search engine, and submits the translated query to the search engine to retrieve information. The system formats resulting information from the search engine into a relational database query result set. Embodiments of the present invention further include a method and computer program product for searching content managed by a search engine in substantially the same manners described above.