CN114756610A - Full-function hybrid data engine management system and method - Google Patents
Full-function hybrid data engine management system and method Download PDFInfo
- Publication number
- CN114756610A CN114756610A CN202210254008.5A CN202210254008A CN114756610A CN 114756610 A CN114756610 A CN 114756610A CN 202210254008 A CN202210254008 A CN 202210254008A CN 114756610 A CN114756610 A CN 114756610A
- Authority
- CN
- China
- Prior art keywords
- data
- database engine
- target
- request
- target data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a full-function hybrid data engine management system and a method. The system comprises: the system comprises a request processing module, a request analysis module and a database engine management module; the request processing module is configured to receive a Structured Query Language (SQL) data request sent by a client and uniformly forward the SQL data request to the request analysis module; the request analysis module is configured to analyze the SQL data request to obtain a target data operation function; wherein the target data manipulation function comprises at least one of a data definition, a data manipulation, and a data query; the database engine management module is configured to select a target database engine from preset database engines to execute a first independent right for realizing the target data operation function. The first claim has the beneficial effect. By adopting the scheme, the problem that full-function data operation cannot be supported is solved, and the effects of managing a plurality of database engines and providing a single entry to execute data operation with different functions can be realized.
Description
Technical Field
The invention relates to the technical field of data management, in particular to a full-function hybrid data engine management system and a full-function hybrid data engine management method.
Background
As the data scenarios to be processed by business applications become more complex, different data engines adaptable to different scenarios are derived.
Nowadays, with a single data engine, fish and bear paw are not available, and multiple data engines must be introduced to enable good support for development and landing of business applications, such as data engine maintenance via direct-connect and routing schemes. However, the above scheme requires the client to know the detail information of the data engine, which results in the details of the data engine being exposed to the outside; meanwhile, the client needs to bind with the data engine, so that the flexibility of selecting the data engine by the client is low.
Disclosure of Invention
The embodiment of the invention provides a full-function hybrid data engine management system and a method thereof, which are used for solving the problem of data management confusion caused by non-uniform interfaces and improving the flexibility of data expansion.
According to an aspect of the present invention, there is provided a full-function hybrid data engine management system, comprising: the system comprises a request processing module, a request analyzing module and a database engine management module; wherein:
the request processing module is configured to receive a Structured Query Language (SQL) data request sent by a client and uniformly forward the SQL data request to the request analysis module;
The request analysis module is configured to analyze the SQL data request to obtain a target data operation function; wherein the target data manipulation function comprises at least one of a data definition, a data manipulation, and a data query;
the database engine management module is configured to select a target database engine from preset database engines to execute the target data operation function.
According to another aspect of the present invention, there is provided a full-function hybrid data engine management method, the method comprising:
receiving a Structured Query Language (SQL) data request sent by a client through a request processing module and uniformly forwarding the SQL data request to a request analysis module;
analyzing the SQL data request through a request analysis module to obtain a target data operation function; wherein the target data manipulation function comprises at least one of a data definition, a data manipulation, and a data query;
and selecting a target database engine from preset database engines to execute the target data operation function through a database engine management module.
In the full-function hybrid data engine management system of the embodiment of the invention, a request processing module receives a Structured Query Language (SQL) data request sent by a client and uniformly forwards the SQL data request to a request analysis module; the request analysis module analyzes the SQL data request to obtain a target data operation function; the target data operation function comprises at least one of data definition, data operation and data query; the database engine management module selects a target database engine from preset database engines to execute the function of realizing target data operation, and a full-function mixed database engine management system with unified metadata is constructed, so that the problem that full-function data operation cannot be supported is solved, and the effects of managing a plurality of database engines and providing a single inlet for executing data operation with different functions can be realized.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a diagram of a direct-coupled multi-database engine management architecture according to an embodiment of the present invention;
FIG. 2 is a simple routing multiple database engine management architecture diagram according to an embodiment of the present invention;
FIG. 3 is a block diagram of a fully functional hybrid data engine management system according to an embodiment of the present invention;
FIG. 4 is a functional diagram of a fully functional hybrid data engine management system, according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a full-featured hybrid data engine management system for data definition according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of a full-function hybrid data engine management system for data manipulation and data query according to an embodiment of the present invention;
fig. 7 is a flowchart of a full-function hybrid data engine management method according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "target," "preset," and the like in the description and claims of the present invention and the above-mentioned drawings are used for distinguishing similar objects and not necessarily for describing a particular order or sequence. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For a client to store and access various types of data engines, two schemes of a direct connection type and a simple routing type exist. Referring to fig. 1, the direct connection type requires binding of a database engine, which has poor flexibility, and a client needs to maintain connection modes and connection information of various data engines. Referring to fig. 2, the simple routing scheme is an improvement over the direct routing scheme, which eliminates the need to maintain connection information for multiple database engines, and is normalized to a single connection, but exposes database engine details. Therefore, how to realize the full function of uniformly managing and guaranteeing data operation for different data engines is particularly important.
Fig. 3 is a block diagram of a full-function hybrid data engine management system according to an embodiment of the present invention, which is applicable to a case where multiple database engines are managed in a unified manner to implement different function data operations. As shown in fig. 3, the system may include: a request processing module 310, a request parsing module 320, and a database engine management module 330. Wherein:
the request processing module 310 is configured to receive a structured query language SQL data request sent by a client and forward the request to the request parsing module 320 in a unified manner.
And the request analysis module 320 is configured to analyze the SQL data request to obtain a target data operation function. Wherein the target data operation function comprises at least one of data definition, data operation and data query.
The database engine management module 330 is configured to select a target database engine from the preset database engines to execute a function of implementing a target data operation.
Referring to fig. 3 and fig. 4, the client may be communicatively connected to the request processing module 310, and the request processing module 310 receives structured query language SQL data requests sent by different clients in real time. The request processing module 310 may uniformly send different structured query language SQL data requests to the request parsing module 320 to instruct the request parsing module 320 to parse the structured query language SQL data requests. Optionally, the structured query language SQL data request may be parsed by the abstract syntax tree AST to obtain the target data manipulation function.
The structured query language SQL divides the data manipulation language DML (e.g. SELECT, Insert, Update, Delete, Truncate, etc. statements), the data definition language DDL (Create, Alter, Drop, etc. statements), and the data control language DCL according to the implementation function. After the SQL data request is analyzed, a target data operation function to be achieved by the SQL data request may be determined from the SQL data request, and the target data operation function may specifically be at least one of a data definition corresponding to a data definition language DDL, a data manipulation language DML data operation, and a data query corresponding to a SELECT statement in a data manipulation language DML.
Referring to fig. 3 and 4, the request processing module 310 is communicatively connected to the database engine management module 330, and the request parsing module 320 informs the database engine management module 330 of the parsed target data operation function. The database engine management module 330 selects a suitable target database engine from a plurality of preset database engines deployed in advance, controls the target database engine to execute a Structured Query Language (SQL) data request sent by a client, and implements a target data operation function. After the implementation of the target data operation function is executed, the execution result can be sequentially returned to the client side upwards.
In an alternative of this embodiment, the request parsing module 320 is further configured to parse the SQL data request to obtain a target data operation requirement of the client; the target data operation requirement is used for describing requirement content involved in the operation of the data table in the database engine.
Accordingly, the request processing module 310 is configured to obtain the target data operation requirement returned by the request parsing module 320 and forward the target data operation requirement to the database engine management module 330.
The database engine management module 330 is configured to select a target database engine from preset database engines according to a target data operation requirement to execute a function of implementing the target data operation.
The request parsing module 320 parses the received SQL data request, which may be obtained including but not limited to the following: and the number of SQL, the type of SQL, the related data table, the database engine where the data table is located, if DDL SQL specifies the type of the engine and the like, and returning. The SQL type is related to data definition, data operation and data query corresponding to the data operation function.
Referring to fig. 5, after the operation function of obtaining the target data is analyzed, when the operation function of the target data is a data definition (such as creating a data table), the operation requirement of the target data includes a database engine category and a data table identifier required for implementing the operation function of the target data. Referring to fig. 6, after the operation function of obtaining the target data through parsing, when the operation function of the target data is an operation data table (such as insert data insert) or a data query (such as query data select), the operation requirement of the target data includes an identifier of the data table required to implement the operation function of the target data, but does not include a category of a database engine required to implement the operation function of the target data.
With the above scheme, the database engine is opaque to the upper layer, the client only knows the engine Category (e.g., OLTP, OLAP, or HTAP) stored in the table, does not sense other details such as the engine type, connection information, and so on, and all the decisions are automatically identified by the request parsing module 320.
Optionally, the preset database engine is a relational database engine, and the preset database engine includes, in terms of functional division, an OLTP transaction-oriented design database engine, an OLAP analytical design database engine, and a transaction and analysis hybrid HTAP database engine. Wherein, OLTP supports affairs, the time delay is low, and the capacity is low; OLAP does not support affairs, and has high time delay and high capacity; HTAP: partial transactions are supported, the time delay is medium, and the capacity is medium. Meanwhile, the preset database engine also comprises a short and bold database engine with weak expansion capability and a database engine supporting horizontal infinite expansion and slow execution according to functional division.
The client accesses the database engine, if the client is a relational database engine, the client can adopt a JDBC mode for connection, and different database engines, JDBC drivers and connection character strings are different. JDBC mode connections are application program interfaces in the Java language that specify how a client program accesses a database, providing methods such as querying and updating data in the database.
In an alternative of this embodiment, referring to fig. 3, the fully functional hybrid data engine management system further comprises a unified metadata management module 340; a unified metadata management module 340 configured to manage metadata information from the data tables to the database engine. The metadata information comprises a data table identifier, a database engine identifier for storing the data table corresponding to the data table identifier, and column data of the data table corresponding to the data table identifier.
By adopting the scheme, all data object metadata information including engines, tables, columns and the like is maintained in a centralized manner, the data acquisition request is received, and the metadata updating request is also received, so that any relational database engine (namely a mixed data engine system) can be supported (accessed) based on unified metadata, and the development and landing of business application supported by introducing various database engines are realized.
In an alternative way to implement the foregoing embodiment, referring to fig. 3 and fig. 5, when the target data operation function is a data definition (for example, creating a data table), the database engine management module 330 is specifically configured to select a target database engine, which is adapted to the class of the database engine indicated by the target data operation requirement, from preset database engines. And the database engine management module 330 is further configured to send the SQL data request to the target database engine, and instruct the target database engine to define data locally according to the data table identifier indicated by the target data operation requirement.
Referring to FIG. 5, when creating a data table, the client declares the database engine requirements, generating an SQL data request for creating the data table. The database engine management module 330 selects the appropriate database engine to create the actual physical table. After the creation is successful, the metadata information of the t1 table is added to the table metadata managed by the unified metadata management module.
In another alternative way to implement the above embodiment, referring to fig. 3 and fig. 6, when the target data operation function is an operation data table (such as insert data insert) or a data query (such as query data select), the request parsing module 320 is further configured to send a data table identifier indicated by a target data operation requirement to the unified metadata management module 340.
The unified metadata management module 340 is configured to query the metadata store for the database engine identifier associated with the data table identifier indicated by the target data operation requirement and return the associated database engine identifier to the request parsing module 320.
Accordingly, the request processing module 310 is configured to forward the database engine identifier associated with the data table identifier indicated by the target data operation requirement to the database engine management module 330.
The database engine management module 330 is configured to use a database engine corresponding to the database engine identifier associated with the data table identifier indicated by the target data operation requirement as a target database engine.
The database engine management module 330 is further configured to send the SQL data request to the target database engine, and instruct the target database engine to perform an operation or query on the data table corresponding to the data table identifier indicated by the operation requirement of the locally stored target data.
Referring to fig. 6, the client only needs to send out the SQL data request, and parses the SQL data request to know that the data table identifier indicated by the target data operation requirement is the t1 table. The unified metadata store is queried to obtain the t1 table on the database engine 1. The SQL data request is sent to the database engine 1, and the database engine 1 performs an operation (such as inserting data) or query on the data table corresponding to the data table identifier indicated by the operation requirement of the locally stored target data. Except for the first table creation, the requirement of a database engine needs to be established, all subsequent operations do not need to know the information of the database engine, and only SQL data request calculation logic is needed.
In an alternative of this embodiment, the request processing module 310 is further configured to notify the metadata management module to update the metadata information from the data table to the database engine after receiving the data defined locally by the target database engine returned by the database engine management module.
According to the technical scheme of the embodiment of the invention, a request processing module receives a Structured Query Language (SQL) data request sent by a client and uniformly forwards the SQL data request to a request analysis module; the request analysis module analyzes the SQL data request to obtain a target data operation function; the target data operation function comprises at least one of data definition, data operation and data query; the database engine management module selects a target database engine from preset database engines to execute a function of realizing target data operation, and a full-function hybrid database engine management system with unified metadata is constructed, so that the problem that full-function data operation cannot be supported is solved, and the effects of managing a plurality of database engines and providing a single entry to execute data operation with different functions can be realized.
Fig. 7 is a flowchart of a full-function hybrid data engine management method according to an embodiment of the present invention, which is applicable to a case where multiple database engines are managed in a unified manner to implement different function data operations, and is applied to the full-function hybrid data engine management system according to the foregoing embodiment. As shown in fig. 3, the method may include:
and S710, receiving the Structured Query Language (SQL) data request sent by the client through the request processing module and uniformly forwarding the SQL data request to the request analysis module.
S720, analyzing the SQL data request through a request analysis module to obtain a target data operation function; wherein the target data manipulation function comprises at least one of a data definition, a data manipulation, and a data query.
And S730, selecting a target database engine from preset database engines through the database engine management module to execute the target data operation function.
On the basis of the foregoing embodiment, optionally, when the target data operation function is obtained by parsing in the SQL data request, the method further includes:
the request analysis module is used for analyzing the SQL data request to obtain the target data operation requirement of the client; the target data operation requirement is used for describing requirement content related to the operation of the data table in the database engine;
Acquiring a target data operation requirement returned by the request analysis module through the request processing module and forwarding the target data operation requirement to the database engine management module;
correspondingly, a target database engine is selected from preset database engines to execute the function of realizing the target data operation, and the method comprises the following steps:
and selecting a target database engine from preset database engines according to the target data operation requirement to execute the target data operation function.
On the basis of the foregoing embodiment, optionally, when the target data operation function is data definition, the target data operation requirement includes a database engine category and a data table identifier required for implementing the target data operation function;
when the target data operation function is an operation data table or data query, the target data operation requirement includes a data table identifier required for realizing the target data operation function, but does not include a database engine category required for realizing the target data operation function.
On the basis of the foregoing embodiment, optionally, the method further includes:
managing metadata information from the data table to a database engine through a unified metadata management module; the metadata information comprises a data table identifier, a database engine identifier for storing the data table corresponding to the data table identifier and column data of the data table corresponding to the data table identifier.
On the basis of the foregoing embodiment, optionally, when the target data operation function is data definition, selecting, by the database engine management module, a target database engine adapted to the database engine category indicated by the target data operation requirement from preset database engines; and sending the SQL data request to the target database engine, and indicating the target database engine to define data locally according to the data table identifier indicated by the target data operation requirement.
On the basis of the above embodiment, optionally, when the target data operation function is data operation or data query, the request parsing module sends the data table identifier indicated by the target data operation requirement to the unified metadata management module;
through the unified metadata management module, a database engine identifier associated with a data table identifier indicated by a target data operation requirement is inquired from a metadata storage and returned to the request analysis module;
through the request processing module, forwarding a database engine identifier associated with the data table identifier indicated by the target data operation requirement to the database engine management module;
Taking a database engine corresponding to a database engine identifier associated with the data table identifier indicated by the target data operation requirement as a target database engine through the database engine management module; and sending the SQL data request to the target database engine, and indicating the target database engine to operate or query the data table corresponding to the data table identifier indicated by the locally stored target data operation requirement.
On the basis of the foregoing embodiment, optionally, the method further includes:
and through the request processing module, after receiving the locally defined data of the target database engine returned by the database engine management module, informing the unified metadata management module to update the metadata information from the data table to the database engine.
On the basis of the foregoing embodiment, optionally, the preset database engine is a relational database engine, and the preset database engine includes, according to functional division, a database engine designed for OLTP transaction type, a database engine designed for OLAP analysis type, and an HTAP database engine with a mixture of transaction and analysis.
The method for managing the full-function hybrid data engine provided by the embodiment of the invention can be applied to the system for managing the full-function hybrid data engine provided by any embodiment of the invention, has the corresponding functions and beneficial effects of the management of the full-function hybrid data engine, and the detailed process refers to the relevant operation of the system for managing the full-function hybrid data engine in the embodiment.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
It is to be noted that the foregoing description is only exemplary of the invention and that the principles of the technology may be employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A full-function hybrid data engine management system, the system comprising: the system comprises a request processing module, a request analyzing module and a database engine management module; wherein:
the request processing module is configured to receive a Structured Query Language (SQL) data request sent by a client and uniformly forward the SQL data request to the request analysis module;
the request analysis module is configured to analyze the SQL data request to obtain a target data operation function; wherein the target data manipulation function comprises at least one of a data definition, a data manipulation, and a data query;
The database engine management module is configured to select a target database engine from preset database engines to execute the function of realizing the target data operation.
2. The system of claim 1, wherein the request resolution module is further configured to: analyzing the SQL data request to obtain the target data operation requirement of the client; the target data operation requirement is used for describing requirement content related to the operation of the data table in the database engine;
the request processing module is configured to acquire a target data operation requirement returned by the request analysis module and forward the target data operation requirement to the database engine management module;
and the database engine management module is configured to select a target database engine from preset database engines according to the target data operation requirement to execute the target data operation function.
3. The system of claim 2,
when the target data operation function is data definition, the target data operation requirement comprises a database engine category and a data table identifier which are required for realizing the target data operation function;
when the target data operation function is an operation data table or data query, the target data operation requirement includes a data table identifier required for realizing the target data operation function, but does not include a database engine category required for realizing the target data operation function.
4. The system of claim 3, further comprising a unified metadata management module; the unified metadata management module is configured to manage metadata information from a data table to a database engine; the metadata information comprises a data table identifier, a database engine identifier for storing the data table corresponding to the data table identifier and column data of the data table corresponding to the data table identifier.
5. The system according to claim 4, wherein when the target data operation function is a data definition, the database engine management module is specifically configured to select a target database engine from preset database engines, where the target database engine is adapted to the database engine category indicated by the target data operation requirement; and sending the SQL data request to the target database engine, and indicating the target database engine to locally define data according to the data table identification indicated by the target data operation requirement.
6. The system according to claim 4, wherein when the target data operation function is a data operation or a data query, the request parsing module is configured to send a data table identifier indicated by the target data operation requirement to the unified metadata management module;
The unified metadata management module is configured to query a database engine identifier associated with the data table identifier indicated by the target data operation requirement from a metadata storage and return the database engine identifier to the request analysis module;
the request processing module is configured to forward a database engine identifier associated with the data table identifier indicated by the target data operation requirement to the database engine management module;
the database engine management module is configured to take a database engine corresponding to a database engine identifier associated with the data table identifier indicated by the target data operation requirement as a target database engine; and sending the SQL data request to the target database engine, and indicating the target database engine to operate or query the data table corresponding to the data table identifier indicated by the operation requirement of the locally stored target data.
7. The system of claim 5, wherein the request processing module is further configured to notify the unified metadata management module to update metadata information of the data table to the database engine after receiving that the database engine management module returns that the target database engine defines data locally.
8. The system of any of claims 1-7, wherein the predetermined database engine is a relational database engine, and wherein the predetermined database engine is functionally partitioned to include an OLTP transactional design oriented database engine, an OLAP analytical design oriented database engine, and a hybrid transactional and analytical HTAP database engine.
9. A method for full-function hybrid data engine management, the method comprising:
receiving a Structured Query Language (SQL) data request sent by a client through a request processing module and uniformly forwarding the request to a request analysis module;
analyzing the SQL data request through a request analysis module to obtain a target data operation function; wherein the target data manipulation function comprises at least one of a data definition, a data manipulation, and a data query;
and selecting a target database engine from preset database engines through a database engine management module to execute the target data operation function.
10. The method of claim 9, wherein when parsing the SQL data request for a target data manipulation function, further comprising:
the request analysis module is used for analyzing the SQL data request to obtain the target data operation requirement of the client; the target data operation requirement is used for describing requirement content related to the operation of the data table in the database engine;
Acquiring a target data operation requirement returned by the request analysis module through the request processing module and forwarding the target data operation requirement to the database engine management module;
correspondingly, a target database engine is selected from preset database engines to execute the function of realizing the target data operation, and the method comprises the following steps:
and selecting a target database engine from preset database engines according to the target data operation requirement to execute the target data operation function.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210254008.5A CN114756610A (en) | 2022-03-15 | 2022-03-15 | Full-function hybrid data engine management system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210254008.5A CN114756610A (en) | 2022-03-15 | 2022-03-15 | Full-function hybrid data engine management system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114756610A true CN114756610A (en) | 2022-07-15 |
Family
ID=82327714
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210254008.5A Pending CN114756610A (en) | 2022-03-15 | 2022-03-15 | Full-function hybrid data engine management system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114756610A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115994146A (en) * | 2023-03-22 | 2023-04-21 | 烟台云朵软件有限公司 | Hybrid data storage engine system, data storage method and access method |
| CN116055325A (en) * | 2022-12-22 | 2023-05-02 | 天翼阅读文化传播有限公司 | Data information management system for interconnection communication |
-
2022
- 2022-03-15 CN CN202210254008.5A patent/CN114756610A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116055325A (en) * | 2022-12-22 | 2023-05-02 | 天翼阅读文化传播有限公司 | Data information management system for interconnection communication |
| CN116055325B (en) * | 2022-12-22 | 2024-04-09 | 天翼阅读文化传播有限公司 | Data information management system for interconnection communication |
| CN115994146A (en) * | 2023-03-22 | 2023-04-21 | 烟台云朵软件有限公司 | Hybrid data storage engine system, data storage method and access method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11580070B2 (en) | Utilizing metadata to prune a data set | |
| CN104620239B (en) | adaptive query optimization | |
| US11468103B2 (en) | Relational modeler and renderer for non-relational data | |
| CN110032604B (en) | Data storage device, translation device and database access method | |
| US10025823B2 (en) | Techniques for evaluating query predicates during in-memory table scans | |
| US6438562B1 (en) | Parallel index maintenance | |
| US7707168B2 (en) | Method and system for data retrieval from heterogeneous data sources | |
| US8924373B2 (en) | Query plans with parameter markers in place of object identifiers | |
| US20160224594A1 (en) | Schema Definition Tool | |
| US20070214104A1 (en) | Method and system for locking execution plan during database migration | |
| CN114756610A (en) | Full-function hybrid data engine management system and method | |
| CN113297320B (en) | Distributed database system and data processing method | |
| US8015165B2 (en) | Efficient path-based operations while searching across versions in a repository | |
| CN109144994A (en) | Index updating method, system and relevant apparatus | |
| JP3742177B2 (en) | Parallel database system routine execution method | |
| CN105975617A (en) | Multi-partition-table inquiring and processing method and device | |
| CN106294695A (en) | A kind of implementation method towards the biggest data search engine | |
| CN106777108A (en) | A kind of data query method and apparatus based on mixing storage architecture | |
| CN106326429A (en) | Hbase second-level query scheme based on solr | |
| US8880463B2 (en) | Standardized framework for reporting archived legacy system data | |
| CN105630881A (en) | Data storage method and query method for RDF (Resource Description Framework) | |
| US20050076018A1 (en) | Sorting result buffer | |
| US20230103328A1 (en) | Data compression techniques | |
| US20200250192A1 (en) | Processing queries associated with multiple file formats based on identified partition and data container objects | |
| CN109815240A (en) | For managing method, apparatus, equipment and the storage medium of index |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |