CN114490842B - Interface data query method and data query engine for multi-source data - Google Patents
Interface data query method and data query engine for multi-source data Download PDFInfo
- Publication number
- CN114490842B CN114490842B CN202111628635.2A CN202111628635A CN114490842B CN 114490842 B CN114490842 B CN 114490842B CN 202111628635 A CN202111628635 A CN 202111628635A CN 114490842 B CN114490842 B CN 114490842B
- Authority
- CN
- China
- Prior art keywords
- query
- database
- data
- target database
- target
- 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.)
- Active
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
-
- 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/21—Design, administration or maintenance of databases
-
- 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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- 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
-
- 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/248—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9532—Query formulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Mathematical Physics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an interface data query method and a data query engine of multi-source data, wherein the method comprises the following steps: a database registration step; a database metadata information acquisition step; a query service; the query interface registers and publishes the service. According to the interface data query method and the data query engine of the multi-source data, when queried data exist in multiple data sources, the multi-source data do not need to be synchronized, and only metadata information of the queried data sources needs to be registered, so that the query function of cross-data-source data can be realized, the query efficiency is improved, and the development cost of data developers is reduced.
Description
Technical Field
The invention belongs to the technical field of computer science, and particularly relates to an interface data query method and a data query engine for multi-source data.
Background
With the improvement of social informatization degree, the data formats inside enterprises are increasingly diversified, data interaction inside and among enterprises is more frequent, and the access to heterogeneous data sources gradually becomes a bottleneck restricting the system. How to improve the interaction efficiency of the system, improve the use efficiency of data in the system, reduce the development cost of developers and shorten the development period becomes a research hotspot.
Based on the above problems, a common solution is to select a data source, then use a data synchronization technology to centralize data tables and data in different data sources in the same data source, and then perform functions such as query processing on the data. Although the method can solve the problem of data isolated island and realize the query of data in multiple data sources, the method still queries a single data source in essence, and for enterprises, when synchronizing data, a corresponding data synchronization function needs to be developed, the integrity and the accuracy of the data during synchronization need to be ensured, the development cost of data developers is increased undoubtedly, and the development period can be prolonged correspondingly.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides an interface data query method and a data query engine of multi-source data, which can effectively solve the problems.
The technical scheme adopted by the invention is as follows:
the invention provides an interface data query method of multi-source data, which comprises the following steps:
step S1, database registration:
establishing a database pool; the database pool is used for storing the driving class and the driving program package of each type of database needing to be connected;
specifically, whenever a database pool is required to be expanded to support a type of database, a driver class and a driver package of the database to be expanded are registered in the database pool;
s2, database metadata information acquisition:
acquiring and managing metadata information and a bottom layer data model of each registered database through a metadata management module, and storing the metadata information and the bottom layer data model of the database into a metadata information base; the metadata information and the bottom layer data model of the database comprise a database name, a database address, a database type and a database port number;
step S3, inquiring service, including:
s3.1, when an SQL query statement of at least one database is received, identifying the SQL query statement of the database through a query statement resolver to obtain a target database name to be queried;
s3.2, judging whether the name of the target database to be inquired is a single database name, if not, judging that the multi-data source is inquired, and executing the step S3.3; if yes, the query is carried out on the single data source, and then the step S3.4 is executed;
step S3.3, splitting the SQL query sentence of the database to obtain the name of each target database;
step S3.4 is executed aiming at each target database name to obtain a query result; then step S3.5 is performed;
s3.4, searching the metadata information base according to the name of the target database to obtain the address of the target database, the type of the target database and the port number of the target database;
then, searching a database pool according to the type of a target database to obtain a drive class and a drive program package corresponding to the type of the target database;
connecting to a target database through the address of the target database and the port number of the target database, and driving the target database through the driving class and the driving program package of the target database so as to establish effective connection with the target database; then, inquiring the target database which is effectively connected to obtain an inquiry result; then step S3.5 is performed;
step S3.5, query result processing:
if the query result is from the same target database, simply packaging the query result to obtain the simply packaged query result, and returning;
if the query result comes from a plurality of target databases, processing the query result according to the query rule, then packaging the query result to obtain a packaged query result, and returning the packaged query result;
step S4, inquiring interface registration and release service:
and after determining that the query result is correct, registering the query statement and the corresponding target database as a query service interface, and issuing the query service interface for other services to call to achieve the function of sharing the data query interface after fully testing the query service interface.
Preferably, in step S3.5, if the query result is from multiple target databases, the query result is determined to be temporarily stored in the memory or the temporary file according to the data amount, and then the query results returned by different databases are processed according to the query conditions and the query logic, so as to generate a final query result set; and packaging the query result set and returning.
The invention also provides a data query engine of the interface data query method of the multi-source data, which comprises the following steps:
the data query engine encapsulates a database pool, a metadata management module, a query statement parser, a query result processing module and a query interface registration module;
the database pool is used for storing the driving class and the driving program package of each type of database to be connected; when the database is connected, the database connected to the corresponding type can be inquired and connected only by providing the correct URL connection address;
the metadata management module is used for acquiring metadata information and a bottom data model of a registered database and providing the metadata information and the bottom data model for the query statement analyzer to use;
the query statement parser is used for automatically identifying the name of the target database to be queried according to the transmitted SQL query statement of the database;
if the data to be queried are from the same target database, obtaining the name of the target database according to the SQL query statement of the database; searching the metadata information base according to the name of the target database to obtain the address of the target database, the type of the target database and the port number of the target database; then, searching a database pool according to the type of a target database to obtain a driving class and a driving program package corresponding to the type of the target database;
connecting to a target database through the address of the target database and the port number of the target database, and driving the target database through the driving class and the driving program package of the target database so as to establish effective connection with the target database; then, inquiring the target database which is effectively connected to obtain an inquiry result;
if the data to be queried comes from at least two target databases, disassembling SQL query statements of the databases, and then performing corresponding database query on each query task to obtain a query result;
the query result processing module is used for uniformly packaging the query results transmitted by the query statement parser; if the query result is from the same target database, simply packaging the query result to obtain the simply packaged query result, and returning;
if the query result comes from a plurality of target databases, processing the query result according to the query rule, then packaging the query result to obtain a packaged query result, and returning the packaged query result;
and the query interface registration module is used for registering the query statement and the corresponding target database as a query service interface after determining that the query result is correct, and issuing the query service interface for other service calls to achieve the function of sharing the data query interface after fully testing the query service interface.
The interface data query method and the data query engine of the multi-source data provided by the invention have the following advantages:
according to the interface data query method and the data query engine of the multi-source data, when queried data exist in multiple data sources, the multi-source data do not need to be synchronized, and only metadata information of the queried data sources needs to be registered, so that the query function of cross-data-source data can be realized, the query efficiency is improved, and the development cost of data developers is reduced.
Drawings
FIG. 1 is a schematic overall flow chart of an interface data query method for multi-source data according to the present invention;
FIG. 2 is a schematic flow chart of the data query steps provided by the present invention;
FIG. 3 is an architecture diagram of the interface data query system for multi-source data provided by the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantageous effects solved by the present invention more clearly apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
The invention aims to solve the problem that when queried data exists in multiple data sources, the data can be queried across the data sources without synchronizing the multi-source data and only by registering metadata information of the queried data sources.
Specifically, the interface query solution of the service-oriented multi-source data is researched and developed by combining the service-oriented idea and the heterogeneous data source-based integration technology. The method designs and realizes a multi-source data Query function in a data service platform, and uses Structured Query Language (SQL) as a Query Language to realize an integrated Query function of relational databases such as mysql database, oracle database and Dammame database which support JDBC specification.
Referring to fig. 1, the present invention provides a method for querying interface data of multi-source data, including the following steps:
step S1, database registration:
establishing a database pool; the database pool is used for storing the driving class and the driving program package of each type of database needing to be connected;
specifically, whenever a database pool is required to be expanded to support a type of database, a driver class and a driver package of the database to be expanded are registered in the database pool;
as a specific implementation, the database pool is used for registering the database types that the service can be connected to. The registered database types need to support JDBC protocol, the driver type and the driver package of each type of database needing to be connected are stored in the database pool, and when the database is connected, the database connected to the corresponding type can be inquired and connected only by providing correct URL connection address and driving through the driver type and the driver package.
S2, database metadata information acquisition:
acquiring and managing metadata information and a bottom layer data model of each registered database through a metadata management module, and storing the metadata information and the bottom layer data model of the database into a metadata information base; the metadata information and the bottom layer data model of the database comprise a database name, a database address, a database type and a database port number;
as a specific implementation manner, the metadata management module is configured to obtain metadata information and an underlying data model of the registered database, and provide the metadata information and the underlying data model for the query service step. The native services may also be managed as a type of metadata to view the service-based data flow.
Step S3, querying the service, referring to fig. 2, includes:
s3.1, when an SQL query statement of at least one database is received, identifying the SQL query statement of the database through a query statement resolver to obtain a target database name to be queried;
s3.2, judging whether the name of the target database to be inquired is a single database name, if not, judging that the target database to be inquired is a multi-data source to be inquired, and executing the step S3.3; if yes, the query is carried out on the single data source, and then the step S3.4 is executed;
s3.3, splitting the SQL query statement of the database to obtain the name of each target database;
step S3.4 is executed aiming at each target database name to obtain a query result; then step S3.5 is performed;
s3.4, searching the metadata information base according to the name of the target database to obtain the address of the target database, the type of the target database and the port number of the target database;
then, searching a database pool according to the type of a target database to obtain a drive class and a drive program package corresponding to the type of the target database;
connecting to a target database through the address of the target database and the port number of the target database, and driving the target database through the driving class and the driving program package of the target database so as to establish effective connection with the target database; then, inquiring the target database which is effectively connected to obtain an inquiry result; then step S3.5 is performed;
as a specific implementation manner, the query statement parser automatically identifies the name of the queried database according to the transmitted SQL query statement, and if the queried data is from the same database, the query statement is directly assigned to the specified database for querying; and if the data are from different databases after the analysis, resolving the query task into the corresponding database query.
Step S3.5, query result processing:
if the query result is from the same target database, simply packaging the query result to obtain the simply packaged query result, and returning;
if the query result comes from a plurality of target databases, processing the query result according to the query rule, then packaging the query result to obtain a packaged query result, and returning the packaged query result;
specifically, if the query result comes from a plurality of target databases, the query result is temporarily stored in a memory or a temporary file according to the data volume, and then the query results returned by different databases are processed according to query logic according to the query condition to generate a final query result set; and packaging the query result set and returning.
Therefore, the query results are uniformly packaged according to the query results transmitted by the query statement parser. If the query result comes from the same database, the query result can be returned only by simply packaging the query result; if the query results come from different databases, the query results are processed according to the query rules and then packaged and returned.
Step S4, inquiring interface registration and release service:
and after the query result is determined to be correct, registering the query statement and the corresponding target database as a query service interface, and issuing the query service interface for other services to call to achieve the function of sharing the data query interface after the query service interface is fully tested.
The updating of the query interface is completed by modifying the query statement, so that the development cost of developers is reduced, and the development period is shortened.
The present invention also provides a data query engine, referring to fig. 3, including:
the data query engine encapsulates a database pool, a metadata management module, a query statement parser, a query result processing module and a query interface registration module;
the database pool is used for storing the driving class and the driving program package of each type of database to be connected; when the database is connected, the database connected to the corresponding type can be inquired and connected only by providing the correct URL connection address;
the metadata management module is used for acquiring metadata information and a bottom data model of a registered database and providing the metadata information and the bottom data model for the query statement analyzer to use;
the query statement parser is used for automatically identifying the name of the target database to be queried according to the transmitted SQL query statement of the database;
if the data to be queried are from the same target database, obtaining the name of the target database according to the SQL query statement of the database; searching the metadata information base according to the name of the target database to obtain the address of the target database, the type of the target database and the port number of the target database; then, searching a database pool according to the type of a target database to obtain a driving class and a driving program package corresponding to the type of the target database;
connecting to a target database through the address of the target database and the port number of the target database, and driving the target database through the driving class and the driving program package of the target database so as to establish effective connection with the target database; then, inquiring the target database which is effectively connected to obtain an inquiry result;
if the data to be queried comes from at least two target databases, disassembling SQL query statements of the databases, and then performing corresponding database query on each query task to obtain a query result;
the query result processing module is used for uniformly packaging the query results transmitted by the query statement parser; if the query result is from the same target database, simply packaging the query result to obtain the simply packaged query result, and returning;
if the query result comes from a plurality of target databases, processing the query result according to the query rule, then packaging the query result to obtain a packaged query result, and returning the packaged query result;
and the query interface registration module is used for registering the query statement and the corresponding target database as a query service interface after determining that the query result is correct, and issuing the query service interface for other service calls to achieve the function of sharing the data query interface after fully testing the query service interface.
In the present invention, the data source and the database refer to the same meaning. One embodiment is described below:
step 1: data source access
(1) Registering existing database connections
The data source access module maintains information related to a database type and a driver class. When adding database connection, selecting relevant database type, filling relevant database connection information, and registering the database in the data source access module.
In the invention, a database pool stores the drive class and the drive program package of each type of database to be connected; but for the same type of database, the connection of a plurality of databases (namely data sources) with the same number can be realized, and the specific connection of the data sources is realized.
(2) Extending new database connections
And (4) placing the connection driving package of the newly expanded database under the relevant path, configuring the driver class, and adding the new type of database connection.
Step 2: database metadata acquisition
And acquiring metadata information of each database, and storing the metadata information (table information and field information of each table) of the connected databases into a metadata information base.
And 3, step 3: data query
The data query method comprises the following specific steps:
(1) Query statement parsing
Analyzing the query sentence, judging whether the query sentence is a single database, if so, directly sending the query sentence to the database for query without processing; if the inquired data is the data of a plurality of databases, the inquiry statement is split, and the relevant data is inquired in the corresponding databases respectively.
(2) Query result processing
If the query result is data returned from the single database, the data is not processed; if the query result is returned from different databases, the returned result is temporarily stored in the memory or a temporary file according to the data volume, then the results returned from different data sources are processed according to the query conditions and the query logic, and then a final result set is generated.
(3) Result return
And packaging the inquired data according to a uniform format, and returning the data to the calling end.
And 4, step 4: interface registration publishing
In the invention, a table is used for storing registered and issued API query interfaces, and the storage information comprises interface paths, corresponding query statement information and the like. After the query statement is confirmed to be correct, a corresponding external query interface is written, and the query interface can be opened.
The interface data query method and the data query engine of the multi-source data provided by the invention have the following advantages:
after registering the data sources, when the interface is queried, the interface query information is analyzed, the query result is obtained after the interface query information is distributed to the corresponding data sources, the corresponding temporary table is registered in the result processing stage, and then data association processing among the cross-data sources is carried out. Therefore, when the inquired data exists in multiple data sources, the multi-source data does not need to be synchronized, and the inquiry function of the data across the data sources can be realized only by registering the metadata information of the inquired data sources, so that the inquiry efficiency is improved, and the development cost of data developers is reduced.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, many modifications and adaptations can be made without departing from the principle of the present invention, and such modifications and adaptations should also be considered to be within the scope of the present invention.
Claims (3)
1. A multi-source data interface data query method is characterized by comprising the following steps:
step S1, a database registration step:
establishing a database pool; the database pool is used for storing the driving classes and the driving program packages of each type of database which needs to be connected;
specifically, when a database pool is required to be expanded to support one type of database, a driver class and a driver package of the database required to be expanded are registered in the database pool;
s2, database metadata information acquisition:
acquiring and managing metadata information and a bottom layer data model of each registered database through a metadata management module, and storing the metadata information and the bottom layer data model of the database into a metadata information base; the metadata information and the bottom layer data model of the database comprise a database name, a database address, a database type and a database port number;
step S3, inquiring service, including:
s3.1, when an SQL query statement of at least one database is received, identifying the SQL query statement of the database through a query statement resolver to obtain a target database name to be queried;
s3.2, judging whether the name of the target database to be inquired is a single database name, if not, judging that the multi-data source is inquired, and executing the step S3.3; if yes, the query is carried out on the single data source, and then the step S3.4 is executed;
s3.3, splitting the SQL query statement of the database to obtain the name of each target database;
step S3.4 is executed aiming at each target database name to obtain a query result; then step S3.5 is performed;
s3.4, searching the metadata information base according to the name of the target database to obtain the address of the target database, the type of the target database and the port number of the target database;
then, searching a database pool according to the type of a target database to obtain a drive class and a drive program package corresponding to the type of the target database;
connecting to a target database through the address of the target database and the port number of the target database, and driving the target database through the driving class and the driving program package of the target database so as to establish effective connection with the target database; then, inquiring the target database which is effectively connected to obtain an inquiry result; then step S3.5 is performed;
step S3.5, query result processing:
if the query result is from the same target database, simply packaging the query result to obtain the simply packaged query result, and returning the query result;
if the query result comes from a plurality of target databases, processing the query result according to the query rule, then packaging the query result to obtain a packaged query result, and returning the packaged query result;
step S4, inquiring interface registration and release service:
and after determining that the query result is correct, registering the query statement and the corresponding target database as a query service interface, and issuing the query service interface for other services to call to achieve the function of sharing the data query interface after fully testing the query service interface.
2. The method for querying interface data of multi-source data according to claim 1, wherein in step S3.5, if the query result is from a plurality of target databases, the query result is temporarily stored in the memory or the temporary file according to the data amount, and then the query results returned from different databases are processed according to the query conditions and the query logic to generate a final query result set; and packaging the query result set and returning.
3. A data query engine system of the multi-source data interface data query method according to any one of claims 1-2, comprising:
the data query engine system is used for packaging a database pool, a metadata management module, a query statement analyzer, a query result processing module and a query interface registration module;
the database pool is used for storing the driving class and the driving program package of each type of database to be connected; when the database is connected, the database connected to the corresponding type can be inquired and connected only by providing the correct URL connection address;
the metadata management module is used for acquiring metadata information and a bottom layer data model of a registered database and providing the metadata information and the bottom layer data model for the query statement analyzer to use;
the query statement parser is used for automatically identifying the name of the target database to be queried according to the transmitted SQL query statement of the database;
if the data to be queried are from the same target database, obtaining the name of the target database according to the SQL query statement of the database; searching the metadata information base according to the name of the target database to obtain the address of the target database, the type of the target database and the port number of the target database; then, searching a database pool according to the type of a target database to obtain a drive class and a drive program package corresponding to the type of the target database;
connecting to a target database through the address of the target database and the port number of the target database, and driving the target database through the driving class and the driving program package of the target database so as to establish effective connection with the target database; then, inquiring the target database which is effectively connected to obtain an inquiry result;
if the data to be queried comes from at least two target databases, disassembling SQL query statements of the databases, and then performing corresponding database query on each query task to obtain a query result;
the query result processing module is used for uniformly packaging the query results transmitted by the query statement parser; if the query result is from the same target database, simply packaging the query result to obtain the simply packaged query result, and returning;
if the query result comes from a plurality of target databases, processing the query result according to the query rule, then packaging the query result to obtain a packaged query result, and returning the packaged query result;
and the query interface registration module is used for registering the query statement and the corresponding target database as a query service interface after determining that the query result is correct, and issuing the query service interface for other service calls to achieve the function of sharing the data query interface after fully testing the query service interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111628635.2A CN114490842B (en) | 2021-12-28 | 2021-12-28 | Interface data query method and data query engine for multi-source data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111628635.2A CN114490842B (en) | 2021-12-28 | 2021-12-28 | Interface data query method and data query engine for multi-source data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114490842A CN114490842A (en) | 2022-05-13 |
| CN114490842B true CN114490842B (en) | 2022-11-11 |
Family
ID=81495370
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111628635.2A Active CN114490842B (en) | 2021-12-28 | 2021-12-28 | Interface data query method and data query engine for multi-source data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114490842B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111435344A (en) * | 2019-01-15 | 2020-07-21 | 中国石油集团川庆钻探工程有限公司长庆钻井总公司 | Big data-based drilling acceleration influence factor analysis model |
| CN111581231A (en) * | 2020-04-20 | 2020-08-25 | 北京明略软件系统有限公司 | Query method and device based on heterogeneous database |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101625690A (en) * | 2009-07-07 | 2010-01-13 | 中国科学院地理科学与资源研究所 | Method and device for sharing access of distributed and heterogeneous earth science data resource |
| CN103617176B (en) * | 2013-11-04 | 2017-03-15 | 广东电子工业研究院有限公司 | One kind realizes the autosynchronous method of multi-source heterogeneous data resource |
| CN109344186A (en) * | 2018-08-23 | 2019-02-15 | 成都四方伟业软件股份有限公司 | A kind of BI system Various database is across the inter-library emerging system in source and fusion method |
| CN110032575A (en) * | 2019-04-15 | 2019-07-19 | 网易（杭州）网络有限公司 | Data query method, apparatus, equipment and storage medium |
| CN110162515A (en) * | 2019-04-30 | 2019-08-23 | 中国科学院深圳先进技术研究院 | A kind of uncoupled elastic data warehouse schema |
| CN110389968A (en) * | 2019-07-31 | 2019-10-29 | 中国工商银行股份有限公司 | Aggregate query method, aggregate query device, equipment and medium |
| CN111737326B (en) * | 2019-10-28 | 2023-08-18 | 埃睿迪信息技术（北京）有限公司 | Method for realizing heterogeneous data source data aggregation in data lake environment |
| CN112925835A (en) * | 2019-12-05 | 2021-06-08 | 北京金山云网络技术有限公司 | Data synchronization method and device and server |
| CN112579625A (en) * | 2020-09-28 | 2021-03-30 | 京信数据科技有限公司 | Multi-source heterogeneous data treatment method and device |
| CN112818051A (en) * | 2021-02-02 | 2021-05-18 | 上海达梦数据库有限公司 | Heterogeneous library communication method, terminal device and storage medium |
-
2021
- 2021-12-28 CN CN202111628635.2A patent/CN114490842B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111435344A (en) * | 2019-01-15 | 2020-07-21 | 中国石油集团川庆钻探工程有限公司长庆钻井总公司 | Big data-based drilling acceleration influence factor analysis model |
| CN111581231A (en) * | 2020-04-20 | 2020-08-25 | 北京明略软件系统有限公司 | Query method and device based on heterogeneous database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114490842A (en) | 2022-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11907247B2 (en) | Metadata hub for metadata models of database objects | |
| US8959106B2 (en) | Class loading using java data cartridges | |
| US9058360B2 (en) | Extensible language framework using data cartridges | |
| JP3742177B2 (en) | Parallel database system routine execution method | |
| US20100228764A1 (en) | Offline Validation of Data in a Database System for Foreign Key Constraints | |
| CN108108456A (en) | A kind of information resources distributed enquiring method based on metadata | |
| CN111078702B (en) | SQL sentence classification management and unified query method and device | |
| US9171036B2 (en) | Batching heterogeneous database commands | |
| CN107291471B (en) | Meta-model framework system supporting customizable data acquisition | |
| US20210209098A1 (en) | Converting database language statements between dialects | |
| CN110019314B (en) | Dynamic data packaging method based on data item analysis, client and server | |
| CN113032423B (en) | Query method and system based on dynamic loading of multiple data engines | |
| CN104794147A (en) | Heterogeneous database access method | |
| US20100049694A1 (en) | Method and system for extending a relational schema | |
| EP4155965A1 (en) | System and method for facilitating metadata identification and import | |
| CN117093599A (en) | Unified SQL query method for heterogeneous data sources | |
| US20220222253A1 (en) | Sql statement generator | |
| CN111694846B (en) | Separation mode distributed storage process implementation method based on Type 2JDBC driver | |
| CN114490842B (en) | Interface data query method and data query engine for multi-source data | |
| CN111782195A (en) | Query method based on adding annotation on request parameter and splicing into SQL | |
| CN116149666A (en) | Grammar checking method and system of SQL sentence, electronic equipment and readable storage medium | |
| US11093492B1 (en) | System and method of fetching data from an external program | |
| WO2023086322A1 (en) | Late materialization of queried data in database cache | |
| CN114547083A (en) | Data processing method and device and electronic equipment | |
| CN110647535A (en) | Method, terminal and storage medium for updating service data to Hive |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |