Dynamic selection of source table for db rollup aggregation and query rewrite based on model driven definitions and cardinality estimates
US-2015379080-A1 · Dec 31, 2015 · US
US2016140205A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016140205-A1 |
| Application number | US-201314787302-A |
| Country | US |
| Kind code | A1 |
| Filing date | Aug 29, 2013 |
| Priority date | Aug 29, 2013 |
| Publication date | May 19, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Described herein are techniques for handling a query that uses first data from a first database and second data from a second database. The first database is accessible via a first execution engine, and the second database is accessible via a second execution engine. A sub-query of the query can be sent to the second execution engine for execution on the second database. Streaming results of the sub-query can be received by the first execution engine.
Opening claim text (preview).
What is claimed is: 1 . A method comprising, by a first execution engine: issuing a query that uses first data stored in a first database and second data stored in a second database, the first execution engine being associated with the first database and a second execution engine being associated with the second database; sending a sub-query of the query to the second execution engine for execution over the second database to retrieve the second data; receiving the second data at the first execution engine in a streaming tuple-by-tuple format from the second execution engine; and executing a remainder of the query. 2 . The method of claim 1 , wherein receiving the second data at the first execution engine in a streaming tuple-by-tuple format from the second execution engine comprises receiving the second data at the first execution engine directly from the second execution engine rather than the second data being materialized in a table before being received by the first execution engine. 3 . The method of claim 1 , wherein the first database is an OLTP database and the second database is an OLAP database. 4 . The method of claim 1 , wherein executing the remainder of the query comprises: retrieving, by the first execution engine, the first data from the first database; and performing, by the first execution engine, at least one operation specified by the query on the first data and the second data. 5 . The method of claim 1 , wherein the first execution engine treats the streaming second data received from the second execution engine as a data source. 6 . A system comprising: a first database accessible via a first execution engine; a second database accessible via a second execution engine, a query executor on the first execution engine to execute a query requiring first data from the first database and second data from the second database, the query comprising a sub-query directed to the second execution engine, the query executor configured to receive streaming query results of the sub-query from the second execution engine. 7 . The system of claim 6 , wherein the first database is an OLTP database storing current data and the second database is an OLAP database storing historical data, the first database storing certain recent data not available on the second database. 8 . The system of claim 6 , wherein the second database is not directly accessible via the first execution engine. 9 . The system of claim 6 , wherein the query executor is configured to send the sub-query to the second execution engine for execution over the second database. 10 . The system of claim 6 , wherein the sub-query is connected to the query via a query connector function that causes the second data to be delivered to the query executor from the second execution engine without any intermediate materialization. 11 . The system of claim 6 , wherein the query executor is further configured to retrieve the first data from the first database and perform at least one operation specified by the query on the first data and the second data. 12 . A non-transitory computer-readable storage medium storing instructions for execution by a computer, the instructions when executed causing an OLTP execution engine to: issue a query requiring first data from an OLTP data source and second data from an OLAP data source, the query comprising a sub-query to obtain the second data; send the sub-query to an OLAP execution engine associated with the OLAP data source; and receive streaming query results corresponding to the sub-query from the OLAP execution engine. 13 . The computer-readable storage medium of claim 12 , the instructions when executed causing the OLTP execution engine to treat the streaming query results corresponding to the sub-query as a data source for the second data. 14 . The computer-readable storage medium of claim 12 , the instructions when executed causing the OLTP execution engine to: retrieve the first data from the OLTP data source using the OLTP execution engine; and perform at least one operation specified by the query on the first data and the second data. 15 . The computer-readable storage medium of claim 12 , wherein the sub-query is connected to the query via a query connector function that causes the second data to be delivered to the OUT execution engine from the OLAP execution engine without any intermediate materialization.
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Distributed queries · CPC title
Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.