CN107783985B - Distributed database query method, device and management system - Google Patents
Distributed database query method, device and management system Download PDFInfo
- Publication number
- CN107783985B CN107783985B CN201610723578.9A CN201610723578A CN107783985B CN 107783985 B CN107783985 B CN 107783985B CN 201610723578 A CN201610723578 A CN 201610723578A CN 107783985 B CN107783985 B CN 107783985B
- Authority
- CN
- China
- Prior art keywords
- query
- execution information
- distributed database
- information
- statement
- 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
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a distributed database query method, which comprises the following steps: searching in a query cache region according to a received query statement, wherein historical execution information is stored in the query cache region; when the history execution information corresponding to the query expression is searched, the query is performed based on the history execution information. The distributed database can save part of the generation process of the execution tree in the query process, thereby reducing the query time delay of the distributed database and improving the concurrency.
Description
Technical Field
The invention relates to the field of distributed databases, in particular to a distributed database query method, a distributed database query device and a distributed database management system.
Background
As the conventional database technology becomes mature and the internet application is developed at a high speed, the database application has been commonly found on the internet. The traditional centralized database system also has the defects that performance bottleneck is caused by adopting centralized management, the single hardware performance improvement cannot meet the requirement of large data volume concurrent query writing of the current internet, and simultaneously, a large amount of hardware maintenance and upgrading cost is generated. In addition, centralized management of databases often causes multiple database associations, and once a database crashes, the entire system crashes. The development of distributed database systems is not prohibitive.
Because data in the distributed database system is located on a large number of different nodes, the performance burden of the system is inevitably increased in the process of inquiring and accessing the data, and the problems of increased inquiry time delay and reduced concurrency are further caused. The existing related distributed query technologies are generally developed on the basis of single-machine data, and the query optimization technologies are still limited in the aspects of caching historical data, caching query execution plans, pre-compiling sentences and the like, and the problems of long query time delay and low concurrency of a distributed database are not solved.
Disclosure of Invention
In order to solve the problems of long query time delay and low concurrency of a distributed database in the related art, the invention provides a distributed database query method, a distributed database query device and a distributed database query management system, so as to at least solve the problems.
According to one aspect of the invention, a distributed database query method is provided, which comprises the following steps: searching in a query cache region according to a received query statement, wherein historical execution information is stored in the query cache region; when the history execution information corresponding to the query expression is searched, the query is performed based on the history execution information.
The historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement position information. When the historical execution information is retrieved, the data node to be queried can be calculated according to the information and the constant value information, and then the query operation is executed.
Optionally, retrieving from the query cache according to the received query statement includes: performing constant replacement on the query statement, and performing hash calculation on the replaced query statement to generate a corresponding hash value; and searching in the query cache according to the hash value.
Optionally, before or after retrieving from the query cache according to the received query statement, the method further includes: collecting execution information in the query process; and under the condition that the execution information accords with the preset rule, storing the execution information into the query cache region.
Optionally, under the condition that it is determined that the preset rule is met, storing the execution information in the query cache includes: and when judging that the inquired data does not need to be subjected to calculation processing, storing the execution information into the inquiry cache region.
According to the invention, retrieval is carried out in the query cache region according to the received query statement, wherein historical execution information is stored in the query cache region; when the history execution information corresponding to the query expression is searched, the query is performed based on the history execution information. The distributed database can save part of the generation process of the execution tree in the query process, thereby reducing the query time delay of the distributed database and improving the concurrency.
According to another aspect of the present invention, there is provided a distributed database query apparatus, disposed in a distributed database management system, including: the retrieval module is used for retrieving in a query cache region according to the received query statement, wherein historical execution information is stored in the query cache region; and an execution module, configured to perform an inquiry according to the historical execution information when the search module searches the historical execution information corresponding to the inquiry statement.
The historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement position information. When the historical execution information is retrieved, the data node to be queried can be calculated according to the information and the constant value information, and then the query operation is executed.
Optionally, the search module includes: the syntax analysis unit is used for performing constant replacement on the query statement, performing hash calculation on the replaced query statement and generating a corresponding hash value; and the retrieval unit is used for retrieving the hash value from the query cache region.
Optionally, the apparatus further comprises: the collection module is used for collecting the execution information in the inquiry process; and the cache module is used for storing the execution information into the query cache region under the condition that the execution information accords with the preset rule.
Optionally, the cache module includes: the judging unit is used for judging whether the inquired data needs to be subjected to calculation processing; and the cache unit is used for storing the execution information into the query cache region when the queried data is judged not to need calculation processing.
According to the invention, a retrieval module retrieves from a query cache region according to a received query statement, wherein historical execution information is stored in the query cache region; and when the execution module searches the historical execution information corresponding to the query statement, the execution module queries according to the historical execution information. The distributed database can save part of the generation process of the execution tree in the query process, thereby reducing the query time delay of the distributed database and improving the concurrency.
According to still another aspect of the present invention, a distributed database management system is provided, which at least includes a distributed database query device and a query cache area. The distributed database query device at least comprises a retrieval module and an execution module, wherein the retrieval module can retrieve in a query cache region according to a received query statement, and historical execution information is stored in the query cache region; the execution module may perform the query based on the history execution information when the search module searches the history execution information corresponding to the query expression.
The historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement position information. When the historical execution information is retrieved, the data node to be queried can be calculated according to the information and the constant value information, and then the query operation is executed.
According to the invention, a retrieval module in the distributed database management system retrieves in a query cache region according to a received query statement, wherein historical execution information is stored in the query cache region; and when the execution module searches the historical execution information corresponding to the query statement, the execution module queries according to the historical execution information. The distributed database can save part of the generation process of the execution tree in the query process, thereby reducing the query time delay of the distributed database and improving the concurrency.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow chart of a distributed database query method according to an embodiment of the invention;
FIG. 2 is a flowchart of a distributed database query method according to an embodiment of the present invention;
FIG. 3 is a flow chart of a distributed database query method according to an embodiment of the invention;
FIG. 4 is a block diagram of a distributed database querying device according to an embodiment of the present invention;
FIG. 5 is a block diagram of a distributed database querying device according to an embodiment of the present invention;
FIG. 6 is a block diagram of a distributed database management system architecture according to an embodiment of the invention;
FIG. 7 is a schematic diagram of a distributed database management system architecture according to an embodiment of the invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
An embodiment of the present invention provides a distributed database query method, and fig. 1 is a first flowchart of the distributed database query method according to the embodiment of the present invention, and as shown in fig. 1, the method includes:
s102, retrieving in a query cache region according to a received query statement, wherein historical execution information is stored in the query cache region;
and S104, when the historical execution information corresponding to the query statement is searched, querying is carried out according to the historical execution information.
The historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement position information. When the historical execution information is retrieved, the data node to be queried can be calculated according to the information and the constant value information, and then the query operation is executed.
According to the embodiment of the invention, retrieval is carried out in a query cache region according to a received query statement, wherein historical execution information is stored in the query cache region; when the history execution information corresponding to the query expression is searched, the query is performed based on the history execution information. The distributed database can save part of the generation process of the execution tree in the query process, thereby reducing the query time delay of the distributed database and improving the concurrency.
In an embodiment of the present invention, fig. 2 is a flowchart of a distributed database query method according to an embodiment of the present invention, and as shown in fig. 2, the step S102 may be further implemented by:
and performing constant replacement on the query statement, performing hash calculation on the replaced query statement to generate a corresponding hash value, and then searching in the query cache region according to the hash value. In this embodiment, the Query statement is an SQL (Structured Query Language) statement.
That is, lexical analysis can be performed on the SQL statement to find constant values in the SQL statement, and the constant values are sequentially recorded in an array, and then the found constant values are replaced by placeholders. And performing hash calculation on the SQL statement after constant replacement to generate a hash value, and taking the hash value as a KEY (KEY) value to search in the query cache region.
For example, the following steps are carried out:
for example, if the query sentence is "Select t1.a from t1where t1.id ═ 30", and the constant value in the query sentence is "30" through lexical analysis, then the placeholder "? "replace it, become" Select t1.a from t1where t1. id? ". Then, carrying out hash calculation on the replaced statement to obtain an integer value: 0x87653127, retrieve the integer value as the KEY value of the query statement from the query cache, and if the same KEY value is retrieved, consider that the historical execution information corresponding to the same KEY value corresponds to the query statement in the present solution, i.e., Select t1.a from t1where t1.id is 30, and then may execute the step S104, that is, continue to perform the query using the historical execution information.
In one embodiment of the present invention, the historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement location information. The table data distribution information may indicate on which nodes the table data are distributed, the destination database information may indicate to which database the query statement should be issued, and the constant replacement position information may indicate where the replaced constant(s) is/are in the query statement. The historical execution information is calculated and cached according to the previous query statement.
When the historical execution information is retrieved according to the new query statement, the data node to be queried can be calculated according to the information and the constant value information, and therefore the corresponding data can be directly obtained from the corresponding data node.
In one embodiment of the present invention, before or after retrieving from the query cache according to the received query statement, the method further includes: collecting execution information in the query process; and under the condition that the execution information accords with the preset rule, storing the execution information into the query cache region. It should be noted that, the step of collecting the execution information in the query process may be before the search step, or after the search step, and there is no restriction on the order; furthermore, after the above-described retrieval step, the execution information in the process of this query can be collected regardless of whether the corresponding historical execution information is retrieved. This embodiment is described only by way of preferred implementation, and fig. 3 is a flowchart of a distributed database query method according to an embodiment of the present invention, as shown in fig. 3, the method includes:
s302, when the query cache is retrieved and the corresponding historical execution information is not retrieved, executing a normal distributed query process on the query statement (i.e. SQL statement).
S304, collecting the execution information of the query in the query process, and judging whether the query statement can be cached or not; wherein, the rule of judging is: if the execution information of the query statement does not need a distributed system to participate in the result set calculation, the result set calculation can be cached; if the distributed system is required to participate in one of grouping, ordering, aggregation calculation, result set deduplication, result set limitation and the like of the result set, the result set cannot be cached.
S306, if the cache can be judged, returning the execution information needing the cache.
S308, caching the execution information into the query cache region for calling when the same or similar statement is sent next time.
An embodiment of the present invention further provides a distributed database query device, which is disposed in a distributed database management system, and fig. 4 is a first structural block diagram of the distributed database query device according to the embodiment of the present invention, and as shown in fig. 4, the device includes: the retrieving module 402 may retrieve from a query cache according to a received query statement, where the query cache stores historical execution information; the execution module 404 may perform the query based on the history execution information when the search module searches the history execution information corresponding to the query expression.
The historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement position information. When the historical execution information is retrieved, the data node to be queried can be calculated according to the information and the constant value information, and then the query operation is executed.
Through the embodiment of the present invention, the retrieval module 402 retrieves from a query cache according to a received query statement, wherein the query cache stores historical execution information; when the execution module 404 retrieves the history execution information corresponding to the query expression, it performs a query based on the history execution information. The distributed database can save part of the generation process of the execution tree in the query process, thereby reducing the query time delay of the distributed database and improving the concurrency.
In an embodiment of the present invention, fig. 5 is a structural block diagram of a distributed database query apparatus according to an embodiment of the present invention, and as shown in fig. 5, the retrieving module 502 further includes a syntax analyzing unit 5002 and a retrieving unit 5004, where the syntax analyzing unit 5002 may perform constant replacement on the query statement, perform hash calculation on the replaced query statement, generate a corresponding hash value, and then retrieve the hash value from the query cache by the retrieving unit 5004. In this embodiment, the query statement is an SQL statement.
That is, the syntax analysis unit 5002 can perform lexical analysis on the SQL statement, find the constant values in the SQL statement, sequentially record the constant values in an array, and then replace the found constant values with placeholders. Then, the SQL statement after constant replacement is hashed to generate a hash value, and the retrieval unit 5004 retrieves the hash value as a KEY value from the query cache.
For example, the following steps are carried out:
for example, if the query statement is "Select t1.a from t1where t1.id ═ 30", the syntax analysis unit 5002 can find out that the constant value is "30" through lexical analysis, and then the placeholder "? "replace it, become" Select t1.a from t1where t1. id? ". Then, carrying out hash calculation on the replaced statement to obtain an integer value: 0x87653127, the retrieving unit 5004 retrieves the integer value as the KEY value of the query statement from the query cache, and if the same KEY value is retrieved, it is determined that the historical execution information corresponding to the same KEY value corresponds to the query statement in the present embodiment, i.e., Select t1.a from t1where t1.id is 30, and then the step S104 may be executed, i.e., the query may be continued by using the historical execution information.
In one embodiment of the present invention, the historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement location information. The table data distribution information may indicate on which nodes the table data are distributed, the destination database information may indicate to which database the query statement should be issued, and the constant replacement position information may indicate where the replaced constant(s) is/are in the query statement. The historical execution information is calculated and cached according to the previous query statement.
When the historical execution information is retrieved according to the new query statement, the data node to be queried can be calculated according to the information and the constant value information, and therefore the corresponding data can be directly obtained from the corresponding data node.
In an embodiment of the present invention, as shown in fig. 5, the apparatus further includes a collecting module 506 and a caching module 508, and further, the caching module 508 further includes a determining unit 5006 and a caching unit 5008.
The collection module 506 may collect the execution information in the query process before or after the retrieval module 502 retrieves the query from the received query statement to the query cache; the cache module 508 may store the execution information in the query cache area when determining that the preset rule is met. It should be noted that, the step of collecting the execution information in the query process may be before the search step, or after the search step, and there is no restriction on the order; furthermore, after the above-described retrieval step, the execution information in the process of this query can be collected regardless of whether the corresponding historical execution information is retrieved. This example is described by way of example of a preferred embodiment, which includes:
s502, when the search module 502 searches the query cache and does not search the corresponding historical execution information, the normal distributed query process is started to be executed on the query statement (i.e. SQL statement).
S504, the collecting module 506 collects the execution information of the query in the querying process, and the determining unit 5006 in the cache module 508 determines whether the query statement can be cached; wherein, the rule of judging is: if the execution information of the query statement does not need a distributed system to participate in the result set calculation, the result set calculation can be cached; if the distributed system is required to participate in one of grouping, ordering, aggregation calculation, result set deduplication, result set limitation and the like of the result set, the result set cannot be cached.
S506, if the determining unit 5006 determines that caching is possible, the execution information that needs to be cached is returned.
S508, the cache unit 5008 in the cache module 508 caches the execution information in the query cache for calling when the same or similar statement is sent next time.
Fig. 6 is a result block diagram of the distributed database management system according to the embodiment of the present invention, and fig. 7 is a schematic diagram of a distributed database management system architecture according to the embodiment of the present invention, and as shown in fig. 6 and fig. 7, the system at least includes a distributed database query device and a query cache region. The distributed database query device at least comprises a retrieval module 502 and an execution module 504, wherein the retrieval module 502 can retrieve in a query cache region according to a received query statement, and historical execution information is stored in the query cache region; the execution module 504 may perform the query based on the history execution information when the search module searches the history execution information corresponding to the query expression.
The historical execution information generally includes one or more items of table data distribution information, destination database information, and constant replacement position information. When the historical execution information is retrieved, the data node to be queried can be calculated according to the information and the constant value information, and then the query operation is executed.
Through the embodiment of the invention, a retrieval module 502 in the distributed database management system retrieves from a query cache region according to a received query statement, wherein historical execution information is stored in the query cache region; when the execution module 504 retrieves the history execution information corresponding to the query expression, it performs a query based on the history execution information. The distributed database can save part of the generation process of the execution tree in the query process, thereby reducing the query time delay of the distributed database and improving the concurrency.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1.A distributed database query method, comprising:
retrieving in a query cache area according to a received query statement, specifically comprising: performing constant replacement on the query statement, and performing hash calculation on the replaced query statement to generate a hash value;
retrieving in the query cache according to the hash value; wherein, historical execution information is stored in the query cache region;
and when the historical execution information corresponding to the query statement is searched, querying according to the historical execution information.
2. The method of claim 1, further comprising, before or after retrieving from the query cache in accordance with the received query statement:
collecting execution information in the query process;
and under the condition that the execution information accords with the preset rule, storing the execution information into the query cache region.
3. The method of claim 2, wherein saving the execution information to the query cache if it is determined that a preset rule is met comprises:
and when judging that the inquired data does not need to be subjected to calculation processing, storing the execution information into the inquiry cache region.
4. The method of claim 1 or 3, wherein the historical execution information comprises at least one of:
table data distribution information, destination database information, and constant replacement position information.
5. A distributed database query device, disposed in a distributed database management system, the distributed database query device comprising:
the retrieval module is used for retrieving in a query cache region according to the received query statement, wherein historical execution information is stored in the query cache region; the retrieval module comprises a syntax analysis unit and a retrieval unit, wherein: the syntax analysis unit is used for performing constant replacement on the query statement and performing hash calculation on the replaced query statement to generate a corresponding hash value, and the retrieval unit is used for retrieving in the query cache region according to the hash value;
and the execution module is used for inquiring according to the historical execution information under the condition that the historical execution information corresponding to the inquiry statement is retrieved by the retrieval module.
6. The apparatus of claim 5, further comprising:
the collection module is used for collecting the execution information in the inquiry process;
and the cache module is used for storing the execution information into the query cache region under the condition that the execution information accords with the preset rule.
7. The apparatus of claim 6, wherein the cache module comprises:
the judging unit is used for judging whether the inquired data needs to be subjected to calculation processing;
and the cache unit is used for storing the execution information into the query cache region when the queried data is judged not to need calculation processing.
8. A distributed database management system, comprising:
the distributed database querying device of any one of claims 5 to 7;
and the query cache region is used for storing historical execution information.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610723578.9A CN107783985B (en) | 2016-08-25 | 2016-08-25 | Distributed database query method, device and management system |
| PCT/CN2017/098886 WO2018036549A1 (en) | 2016-08-25 | 2017-08-24 | Distributed database query method and device, and management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610723578.9A CN107783985B (en) | 2016-08-25 | 2016-08-25 | Distributed database query method, device and management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107783985A CN107783985A (en) | 2018-03-09 |
| CN107783985B true CN107783985B (en) | 2021-04-16 |
Family
ID=61245492
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610723578.9A Active CN107783985B (en) | 2016-08-25 | 2016-08-25 | Distributed database query method, device and management system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107783985B (en) |
| WO (1) | WO2018036549A1 (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110008448B (en) * | 2019-04-02 | 2023-10-17 | 中国工商银行股份有限公司 | Method and device for automatically converting SQL code into Java code |
| CN111309724A (en) * | 2019-12-31 | 2020-06-19 | 航天信息股份有限公司 | Method and system for processing big data |
| CN111291054B (en) * | 2020-02-21 | 2023-05-16 | 苏宁云计算有限公司 | Data processing method, device, computer equipment and storage medium |
| CN111639140A (en) * | 2020-06-08 | 2020-09-08 | 杭州复杂美科技有限公司 | Distributed data storage method, device and storage medium |
| CN112597004A (en) * | 2020-12-11 | 2021-04-02 | 广州品唯软件有限公司 | SQL statement performance test method and device, computer equipment and storage medium |
| CN113064912B (en) * | 2021-03-24 | 2023-07-21 | 西安热工研究院有限公司 | Method for quickly inquiring historical alarm information in DCS background |
| CN113377764B (en) * | 2021-05-07 | 2024-04-12 | 北京锐服信科技有限公司 | PCAP data packet high-speed indexing method and system |
| CN114238404A (en) * | 2021-12-15 | 2022-03-25 | 建信金融科技有限责任公司 | Data query method and device, storage medium and equipment |
| CN116541420B (en) * | 2023-07-07 | 2023-09-15 | 上海爱可生信息技术股份有限公司 | Vector data query method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102646130A (en) * | 2012-03-12 | 2012-08-22 | 华中科技大学 | Method for storing and indexing mass historical data |
| CN104216894A (en) * | 2013-05-31 | 2014-12-17 | 国际商业机器公司 | Method and system for data query |
| CN104216955A (en) * | 2014-08-20 | 2014-12-17 | 百度在线网络技术（北京）有限公司 | Methods and devices for operating data and managing events and distributed system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101930472A (en) * | 2010-09-09 | 2010-12-29 | 南京中兴特种软件有限责任公司 | Parallel query method for distributed database |
-
2016
- 2016-08-25 CN CN201610723578.9A patent/CN107783985B/en active Active
-
2017
- 2017-08-24 WO PCT/CN2017/098886 patent/WO2018036549A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102646130A (en) * | 2012-03-12 | 2012-08-22 | 华中科技大学 | Method for storing and indexing mass historical data |
| CN104216894A (en) * | 2013-05-31 | 2014-12-17 | 国际商业机器公司 | Method and system for data query |
| CN104216955A (en) * | 2014-08-20 | 2014-12-17 | 百度在线网络技术（北京）有限公司 | Methods and devices for operating data and managing events and distributed system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107783985A (en) | 2018-03-09 |
| WO2018036549A1 (en) | 2018-03-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107783985B (en) | Distributed database query method, device and management system | |
| US20220405284A1 (en) | Geo-scale analytics with bandwidth and regulatory constraints | |
| US11182356B2 (en) | Indexing for evolving large-scale datasets in multi-master hybrid transactional and analytical processing systems | |
| US20070233720A1 (en) | Lazy bulk insertion method for moving object indexing | |
| US10565201B2 (en) | Query processing management in a database management system | |
| JP2004518226A (en) | Database system and query optimizer | |
| US9229960B2 (en) | Database management delete efficiency | |
| CN109947796B (en) | Caching method for query intermediate result set of distributed database system | |
| US10685031B2 (en) | Dynamic hash partitioning for large-scale database management systems | |
| CN108509453B (en) | Information processing method and device | |
| US20150199408A1 (en) | Systems and methods for a high speed query infrastructure | |
| CN110889023A (en) | Distributed multifunctional search engine of elastic search | |
| JP2020123320A (en) | Method, apparatus, device and storage medium for managing index | |
| CN111752945B (en) | Time sequence database data interaction method and system based on container and hierarchical model | |
| US8756246B2 (en) | Method and system for caching lexical mappings for RDF data | |
| US7676457B2 (en) | Automatic index based query optimization | |
| CN107609091B (en) | Method for realizing cross-database multi-table combined query system | |
| US20140258264A1 (en) | Management of searches in a database system | |
| US8200673B2 (en) | System and method for on-demand indexing | |
| KR101955376B1 (en) | Processing method for a relational query in distributed stream processing engine based on shared-nothing architecture, recording medium and device for performing the method | |
| CN111611222A (en) | Data dynamic processing method based on distributed storage | |
| CN115391424A (en) | Database query processing method, storage medium and computer equipment | |
| CN108804502A (en) | Big data inquiry system, method, computer equipment and storage medium | |
| KR101223813B1 (en) | Apparatus and Method for information search by inquiry | |
| Ragavan | Efficient key hash indexing scheme with page rank for category based search engine big data |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220105 Address after: 100176 602, floor 6, building 6, courtyard 10, KEGU 1st Street, Beijing Economic and Technological Development Zone, Daxing District, Beijing (Yizhuang group, high-end industrial area of Beijing Pilot Free Trade Zone) Patentee after: Jinzhuan Xinke Co.,Ltd. Address before: 518057 Zhongxing building, science and technology south road, Nanshan District hi tech Industrial Park, Guangdong, Shenzhen Patentee before: ZTE Corp. |
|
| TR01 | Transfer of patent right |