# US 2022/0012238 A1 · Datacube access connectors

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0012238 A1
- Document ID: US20220012238A1
- Status: Published application
- Kind: A1
- Application number: 17/368,937
- Filed: 2021-07-07
- Published: 2022-01-13
- Earliest claimed: 2020-07-07
- Assignees: AtScale, Inc.
- Applicants: AtScale, Inc.
- Inventors: Sarah Gerweck
- Web page: https://patentgrep.com/patent/US20220012238A1

## CPC

- G06F 16/2455: Query execution
- G06F 16/283: {Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP}
- G06F 16/2425: {Iterative querying; Query formulation based on the results of a preceding query}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A multidimensional database query engine processes a query request by forming a logical plan of subqueries for retrieving and assembling the data called for by the query request. A multidimensional database connector is invoked to transform a logical plan that defines and orders each subquery into a physical plan for accessing the data repositories where the data satisfying the query is stored. The query engine is invoked or called by an application and receives a query plan indicative of data repositories interrogated by query instructions in the query plan. For each data repository of the plurality of data repositories that may be interrogated by the query plan, a connector is defined based on commands for accessing each data repository. The connector associates each query instruction from the query plan with a corresponding repository command for accessing the data repository.

## Claims

### Claim 1

In a datacube environment having a plurality of dimensions indicative of facts, a method for accessing data in fact tables, comprising:
receiving a query plan, the query plan indicative of data repositories interrogated by query instructions in the query plan;
establishing, for each data repository of a plurality of data repositories interrogated by the query plan, a connector based on commands for accessing each data repository, the connector associating a query instruction from the query plan with a corresponding repository command for accessing the data repository; and
isolating, for each established connector, query instructions and associated repository commands from the query instructions and associated repository commands of the other connectors established for the plurality of data repositories.

### Claim 2 (depends on 1)

The method of claim 1 wherein the query plan includes a plurality of subqueries, each subquery in the plurality of subqueries accessing at least one data repository using a mapping of, for each data repository, query instructions to repository commands called for by the subqueries.

### Claim 3 (depends on 2)

The method of claim 2 wherein each subquery in the plurality of subqueries includes at least one query instruction, further comprising:
identifying, for the query instruction, a corresponding repository command for accessing the data repository.

### Claim 4 (depends on 2)

The method of claim 2 wherein the data repository includes one or more fact tables, the fact tables responsive to the repository commands for retrieving data items stored in the fact table for satisfying the subquery accessing the data repository.

### Claim 5 (depends on 1)

The method of claim 1 further comprising generating the query plan by:
generating a set of subqueries based on dependencies between data items sought by the query and an ordering of query operations; and
ordering the generated subqueries in the query plan for defining a sequence and dependence between the generated subqueries.

### Claim 6 (depends on 1)

The method of claim 1 further comprising:
invoking the connector from a subquery of the plurality of subqueries;
accessing code or libraries for execution of the repository commands; and
instantiating a set of instructions based on the accessed code or libraries for performing the repository commands in a noninterfering manner with other invoked connectors.

### Claim 7 (depends on 1)

The method of claim 1 further comprising registering the connectors by:
receiving an identification of the connectors required by the subqueries called for by the query plan;
identifying a storage location for access by each of the connectors; and
loading, prior to execution of a query plan, the connectors for accessing the respective identified storage location.

### Claim 8 (depends on 3)

The method of claim 3 further comprising rendering a textual representation of the repository command identified from the query instruction.

### Claim 9 (depends on 3)

The method of claim 3 wherein further comprising mapping the query instruction from the subquery to a repository instruction recognized by the data repository.

### Claim 10 (depends on 9)

The method of claim 9 wherein the mapping further comprising launching an executable set of instructions for performing the subquery.

### Claim 11

A data structure for, in a datacube environment having a plurality of dimensions indicative of facts, accessing data in fact tables, comprising:
a query plan, the query plan indicative of data repositories interrogated by query instructions in the query plan; and
a registry for storing, for each data repository of a plurality of data repositories interrogated by the query plan, a connector based on commands for accessing each data repository, the connector associating a query instruction from the query plan with a corresponding repository command for accessing the data repository,
the connector configured for isolating, for each established connector, query instructions and associated repository commands from the query instructions and associated repository commands of the other connectors established for the plurality of data repositories.

### Claim 12 (depends on 11)

The data structure of claim 11 wherein the query plan includes a plurality of subqueries, each subquery in the plurality of subqueries accessing at least one data repository using a mapping of, for each data repository, query instructions to repository commands called for by the subqueries.

### Claim 13 (depends on 12)

The data structure of claim 12 wherein each subquery in the plurality of subqueries includes at least one query instruction, the connector further configured for identifying, for the query instruction, a corresponding repository command for accessing the data repository.

### Claim 14 (depends on 12)

The data structure of claim 12 wherein the data repository includes one or more fact tables, the fact tables responsive to the repository commands for retrieving data items stored in the fact table for satisfying the subquery accessing the data repository.

### Claim 15 (depends on 11)

The data structure of claim 11 wherein query plan is responsive to:
generating a set of subqueries based on dependencies between data items sought by the query and an ordering of query operations; and
ordering the generated subqueries in the query plan for defining a sequence and dependence between the generated subqueries.

### Claim 16

A computer program embodying program code on a non-transitory medium that, when executed by a processor, performs steps for implementing a method for, in a datacube environment having a plurality of dimensions indicative of facts, a method for accessing data in fact tables, the method comprising:
receiving a query plan, the query plan indicative of data repositories interrogated by query instructions in the query plan;
establishing, for each data repository of a plurality of data repositories interrogated by the query plan, a connector based on commands for accessing each data repository, the connector associating a query instruction from the query plan with a corresponding repository command for accessing the data repository; and
isolating, for each established connector, query instructions and associated repository commands from the query instructions and associated repository commands of the other connectors established for the plurality of data repositories.
