US 11,907,216 B2Granted

Multi-language fusion query method and multi-model database system

AssigneeHuawei Technologies Co., Ltd.

InventorMinqi Zhou

Life of this patent

Estimating the term…

Loading patent…

Abstract

A fusion query method and a multi-model database (MMDB) framework are provided, to add a capability of extending a foreign engine in a relational database engine and manage metadata of the foreign extensible engine by using a user table. This minimizes intrusion to the relational database engine, and implements dynamic loading and unloading of the foreign engine during runtime. Therefore, a maintenance interface and uniform data access to a multi-model database such as a relational database, a graph database, or a time series database are provided for a user, so that learning and use costs of operation and maintenance personnel and application development personnel are reduced, and security of data use is improved.

Claims14

Dependent claims

A multi-model database management system, comprising a main execution engine, one or more extensible execution engines, and an adapter, wherein

the main execution engine is configured to:
receive a fusion query from a client, wherein the fusion query comprises a first type of query and a second type of query;
process the first type of query to obtain a first processing result;
and
pass the second type of query to the adapter by using a first interface;
the adapter is configured to:
determine, based on metadata of the one or more extensible execution engines, a first extensible execution engine configured to process the second type of query, and a second interface corresponding to the first extensible execution engine;
and
pass the second type of query to the first extensible execution engine by using the second interface;
the first extensible execution engine is configured to:
process the second type of query to obtain a second processing result;
and
return the second processing result to the main execution engine by using the adapter;
and
the main execution engine is further configured to:
generate a query result based on the first processing result and the second processing result;
and
return the query result to the client,
wherein the metadata comprises information about an extensible execution engine supported by the multi-model database management system,
wherein the information about the extensible execution engine comprises:
a type of the extensible execution engine, an address of a server on which one or more instances of the extensible execution engine are located, and interface information corresponding to the extensible execution engine.

18 more elements

A database server, comprising a processor, a memory, and a computer program that is stored in the memory and executable by the processor, wherein when the processor executes the program the processer is configured to:

receive a fusion query submitted by a client, wherein the fusion query comprises a first type of query and a second type of query;
process, by using a main execution engine, the first type of query to obtain a first processing result;
determine, based on metadata, a first extensible execution engine configured to process the second type of query, and an interface corresponding to the first extensible execution engine wherein the metadata comprises information about an extensible execution engine supported by a multi-model database management system, and the information about the extensible execution comprises a type of the extensible executing engine and an address of a server on which one or more instances of the extensible execution engine are located;
pass, by using the interface, the second type of query to the first extensible execution engine;
process, by using the first extensible execution engine, the second type of query to obtain a second processing result;
and
generate a query result based on the first processing result and the second processing result, and returning the query result to the client.

4 more elements

A fusion query method, comprising:

receiving a fusion query submitted by a client, wherein the fusion query comprises a first type of query and a second type of query;
processing, by using a main execution engine, the first type of query to obtain a first processing result;
determining, based on metadata, a first extensible execution engine configured to process the second type of query, and an interface corresponding to the first extensible execution engine, wherein the metadata comprises information about an extensible execution engine supported by a multi-model database management system, and the information about the extensible execution engine comprises a type of the extensible execution engine and an address of a server on which one or more instances of the extensible execution engine are located;
passing, by using the interface, the second type of query to the first extensible execution engine;
processing, by using the first extensible execution engine, the second type of query to obtain a second processing result;
and
generating a query result based on the first processing result and the second processing result, and returning the query result to the client.

4 more elements

Dependencies are inferred from the claim text.

Facts

Application: 17/525,792Filed 12 Nov 2021 · continuation
Priority: CN 201910403857.015 May 2019
Published: US 2022/0075780 A110 Mar 2022
Granted: 20 Feb 2024
Term ends: Not estimatedThe source records don’t support an estimate.

Classification7 codes

G06F 16/22
Of structured data, e.g. relational data: indexing; Data structures therefor; Storage structures
G06F 16/24542
Query rewriting; Transformation: plan optimisation
G06F 16/2282
Indexing; Data structures therefor; Storage structures: tablespace storage structures; Management thereof
G06F 16/245
Querying: query processing

Family

PCT/CN2020/090393Parent of this continuation · filed 15 May 2020
US 2022/0075780 A1Pre-grant publication · published 10 Mar 2022
US 11,907,216 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key