Query routing method, query routing server performing the same and storage medium storing the same
AssigneeLG Cns Co., Ltd.
InventorsSeokkeun Oh, Hyunsang Kang, Jongwon Park, Jooyoul Lee, Donjung Choi
Life of this patent
Estimating the term…
Abstract
Provided is a method, server, and storage medium for query routing. A query may be processed on a query routing server using a same distributed file system and connectable with a plurality of query performance engines sharing metadata. The method may include receiving, through a user input interface, a query and a criterion to select a query performance engine among a plurality of query performance engines, and determining, by a query routing server, one of the plurality of query performance engines based on the received criterion.
Claims18
A method for routing a query performed on a query routing server using a same distributed file system and being connectable with a plurality of query performance engines sharing metadata, the plurality of query performance engines includes a first query performance engine and a second query performance engine which are different types of query performance engines, the method comprising:
- receiving, through a user input interface, a query and a criterion to select a query performance engine among a plurality of query performance engines;
- and
- determining, by a query routing server, one of the plurality of query performance engines based on the received criterion,
- wherein determining one of the plurality of query performance engines includes detecting a type of the received query to determine a query performance engine between the first query performance engine or the second query performance engine that is most optimized for the query type among the plurality of query performance engines, and
- wherein the query type is determined based on a query execution plan (QEP), the QEP including information for whether an operator included in the query is configured for parallel processing or whether there is another applicable operator more suitable for performing the query to replace the operator included in the query.
A query routing server using a same distributed file system and being connectable with a plurality of query performance engines sharing metadata, the server comprising:
- at least one processor;
- at least one memory;
- a user interface;
- a query and criterion receiving unit that receives, through the user interface, a query and a criterion to select a query performance engine among a plurality of query performance engines, the plurality of query performance engines includes a first query performance engine and a second query performance engine which are different types of query performance engines;
- and
- a query performance engine determining unit that determines one of the plurality of query performance engines based on the received criterion,
- wherein determining one of the plurality of query performance engines includes detecting a type of the received query to determine a query performance engine between the first query performance engine or the second query performance engine that is most optimized for the query type among the plurality of query performance engines, and
- wherein the query type is determined based on a query execution plan (QEP), the QEP including information for whether an operator included in the query is configured for parallel processing or whether there is another applicable operator more suitable for performing the query to replace the operator included in the query.
A machine-readable non-transitory medium storing a computer program for a query routing method, the method being performed on a query routing server using a same distributed file system and being connectable with a plurality of query performance engines sharing metadata, wherein the plurality of query performance engines includes a first query performance engine and a second query performance engine which are different types of query performance engines, the machine-readable non-transitory medium having stored thereon machine-executable instructions for:
- receiving a query and a criterion to select a query performance engine among a plurality of query performance engines;
- and
- determining one of the plurality of query performance engines based on the received criterion,
- wherein determining one of the plurality of query performance engines includes detecting a type of the received query to determine a query performance engine between the first query performance engine or the second query performance engine that is most optimized for the query type among the plurality of query performance engines, and
- wherein the query type is determined based on a query execution plan (QEP), the QEP including information for whether an operator included in the query is configured for parallel processing or whether there is another applicable operator more suitable for performing the query to replace the operator included in the query.
Dependencies are inferred from the claim text.