Queries involving multiple databases and execution engines

US2016140205A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016140205-A1
Application numberUS-201314787302-A
CountryUS
Kind codeA1
Filing dateAug 29, 2013
Priority dateAug 29, 2013
Publication dateMay 19, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

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.

First claim

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.

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016140205A1 cover?
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 th…
Who is the assignee on this patent?
Hewlett Packard Development Co
What technology area does this patent fall under?
Primary CPC classification G06F17/30592. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu May 19 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).