Parallel processing database system

US2018011902A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2018011902-A1
Application numberUS-201715714637-A
CountryUS
Kind codeA1
Filing dateSep 25, 2017
Priority dateFeb 25, 2013
Publication dateJan 11, 2018
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.

A method and system for executing database queries in parallel using a shared metadata store. The metadata store may reside on a master node, where the master node is the root node in a tree. The master node may distribute query plans and query metadata to other nodes in the cluster. These additional nodes may request additional metadata from each other or the master nodes as necessary.

First claim

Opening claim text (preview).

What is claimed is: 1 . A parallel processing database system, comprising: a database catalog associated with a master node comprising metadata defining database objects; the master node, wherein the master node comprises one or more processors, wherein the master node is configured to receive a query from a client node, to obtain metadata from the database catalog using a catalog server session that is established in connection with the query, to send one or more query plans and corresponding metadata to one or more of a plurality of worker nodes, and to obtain additional metadata to be used in connection with execution of the corresponding query plan from the database catalog using the catalog server session that was established in connection with the query, and to provide the addition metadata to one or more of the plurality of worker nodes; and the plurality of worker nodes in communication with the master node, wherein one or more of the plurality of worker nodes are configured to use the corresponding query metadata received from the master node in connection with execution of the one or more query plans. 2 . The system of claim 1 , wherein the master node is further configured to receive a request from a first worker node of the one or more of the plurality of worker nodes, the request being for additional metadata to be used in connection with execution of the corresponding query plan, and wherein the additional metadata is obtained in response to the master node receiving the request for additional metadata. 3 . The system of claim 2 , wherein the request for additional metadata is received from a first worker node in the event that the first worker node determines that received corresponding query metadata is not sufficient to execute the corresponding query plan, and in the event that at least one other worker node of the plurality of worker nodes is queried for the additional metadata and the at least one other worker node does not have the additional metadata. 4 . The system of claim 1 , wherein individual nodes of the plurality of worker nodes include a cache. 5 . The system of claim 4 , wherein the received query metadata is stored in the cache of the individual nodes. 6 . The system of claim 1 , wherein the master node and the plurality of worker nodes have a tree configuration. 7 . The system of claim 6 , wherein the master node is a root node. 8 . The system of claim 1 , wherein an individual node of the plurality of worker nodes requests additional metadata from the master node. 9 . The system of claim 1 , wherein an individual node of the plurality of worker nodes requests additional metadata from a parent node. 10 . The system of claim 9 , wherein the parent node is another worker node. 11 . The system of claim 1 , wherein the database objects comprise database table definitions, database functions, database users, database views, and database indexes. 12 . The system of claim 1 , wherein the master node receives the query from the client, develops the one or more query plans based at least in part on the query, and communicates each of the one or more query plans to a corresponding one of the plurality of worker nodes in connection with metadata from the database catalog that is determined to be required for execution of the query plan. 13 . The system of claim 1 , wherein in response to receiving the query, the catalog server session is established, and the corresponding query metadata is retrieved in the catalog server session. 14 . The system of claim 13 , wherein in the event that a first worker node requests additional query metadata to be used in connection with the execution of the corresponding query plan, the additional query metadata is retrieved using the catalog server session that was established in connection with the received query. 15 . The system of claim 1 , wherein in the event that metadata stored in the database catalog is updated at a time between when metadata to be sent in connection with the one or more query plans is obtained from the database catalog and when the request for additional metadata is received by the master node, the additional metadata is obtained from the database catalog using the catalog server session that was established in connection with the query such that the additional metadata does not include the updated metadata. 16 . The system of claim 1 , wherein a first worker node of the plurality of worker nodes determines that the received corresponding query metadata is not sufficient to execute the corresponding query plan, and in response to determining that the received corresponding query metadata is not sufficient to execute the corresponding query plan requests additional metadata from one or more other of the plurality of worker nodes. 17 . The system of claim 16 , wherein the master node is queried for the additional metadata after the one or more other of the plurality of worker nodes are requested for the additional metadata. 18 . The system of claim 16 , wherein the master node and the plurality of worker nodes have a tree configuration, and the one or more other of the plurality of worker nodes are queried for additional metadata based at least in part on the tree configuration. 19 . A method comprising: receiving, by a master node, a query from a client node, wherein the master node is associated with at least one processor configured to communicate with a database catalog that includes metadata defining database objects, and wherein the master node is in communication with a plurality of worker nodes; obtaining, by the master node, metadata from the database catalog using a catalog server session that is established in connection with the query; sending, by the master node, a corresponding query plan and corresponding query metadata to one or more of the plurality of worker nodes, wherein the one or more of the plurality of worker nodes are configured to use the corresponding query metadata received from the master node in connection with execution of the corresponding query plan; obtaining, by the master node, additional metadata to be used in connection with execution of the corresponding query from the database catalog using the catalog server session that was established in connection with the query; and providing the addition metadata to one or more of the plurality of worker nodes. 20 . A computer program product embodied in a tangible non-transitory computer-readable storage medium and comprising computer instructions for: receiving, by a master node, a query from a client node, wherein the master node is associated with a database catalog that includes metadata defining database objects, and wherein the master node is in communication with a plurality of worker nodes; obtaining, by the master node, metadata from the database catalog using a catalog server session that is established in connection with the query; sending, by the master node, a corresponding query plan and corresponding query metadata to one or more of the plurality of worker nodes, wherein the one or more of the plurality of worker nodes are configured to use the corresponding query metadata received from the master node in connection with execution of the corresponding query plan; obtaining, by the master node, additional metadata to be used in connection with execution of the corresponding query from the database catalog using the catalog server session that was established in connection with the query; and providing the add

Assignees

Inventors

Classifications

  • Plan optimisation · CPC title

  • Access plan code generation and invalidation; Reuse of access plans · CPC title

  • Parallel file systems, i.e. file systems supporting multiple processors · CPC title

  • File systems; File servers · CPC title

  • of parallel queries · CPC title

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 US2018011902A1 cover?
A method and system for executing database queries in parallel using a shared metadata store. The metadata store may reside on a master node, where the master node is the root node in a tree. The master node may distribute query plans and query metadata to other nodes in the cluster. These additional nodes may request additional metadata from each other or the master nodes as necessary.
Who is the assignee on this patent?
Emc Ip Holding Co Llc
What technology area does this patent fall under?
Primary CPC classification G06F16/24542. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Jan 11 2018 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).