WO2024040784A1 - 一种基于云计算的数据检索方法、装置及系统 - Google Patents
一种基于云计算的数据检索方法、装置及系统 Download PDFInfo
- Publication number
- WO2024040784A1 WO2024040784A1 PCT/CN2022/135924 CN2022135924W WO2024040784A1 WO 2024040784 A1 WO2024040784 A1 WO 2024040784A1 CN 2022135924 W CN2022135924 W CN 2022135924W WO 2024040784 A1 WO2024040784 A1 WO 2024040784A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- retrieval
- data
- level cache
- request field
- request
- 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.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/245—Query processing
- G06F16/2453—Query optimisation
- G06F16/24534—Query rewriting; Transformation
- G06F16/24539—Query rewriting; Transformation using cached or materialised query results
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Definitions
- the present invention relates to the field of data processing technology, and in particular to a data retrieval method, device and system based on cloud computing.
- each search engine is connected to a different cloud database, and each search engine is loaded with a unified search service.
- users perform data retrieval, they call unified retrieval services in each search engine to retrieve data results from each cloud database, and then integrate the data results.
- Embodiments of the present invention provide a data retrieval method, device and system based on cloud computing, which are used to adaptively retrieve data results from each cloud database, improve the accuracy of retrieval data, avoid redevelopment of business logic, and reduce business logic Development difficulty and maintenance costs.
- embodiments of the present invention provide a data retrieval method based on cloud computing, including:
- the retrieval request includes a first request field
- a second request field that satisfies the retrieval condition is generated; the first request field is different from the second request field; the retrieval condition is generated based on a field of data in the cloud database, indicating Fields in the cloud database that allow indexing data;
- the data retrieval method based on cloud computing is applied to the data retrieval system.
- the system includes a scheduling service and multiple retrieval engines; among them, the retrieval conditions of multiple retrieval engines are different; for any retrieval engine, the retrieval engine's
- the search conditions are generated based on the fields of the data in the cloud database connected to the search engine, indicating the fields in the cloud database that allow indexing of data.
- the scheduling service is used to obtain the retrieval request sent by the user, and after obtaining the retrieval request, sends the retrieval request to each retrieval engine, and each retrieval engine retrieves data from the corresponding cloud database.
- the search engine has preset search conditions.
- the search engine will generate a second request field based on the first request field according to the corresponding search conditions.
- the second request field satisfies the search conditions, and then when retrieving data in the cloud database based on the second request field, the accuracy of the retrieved data is guaranteed.
- There is no need to set up search services in each search engine which avoids the redevelopment of business logic and reduces the difficulty of business logic development and maintenance costs.
- the first search result after obtaining the first search result, it also includes:
- the first level cache space After deduplicating the homogeneous data in the first search result, cache the deduplicated first search result to the first level cache space to obtain the first level cache data; the first level cache space includes a first condition sequence list ; The first condition sequence list records the mapping relationship between the first request field and the first-level index; the first-level index is used to index the first-level cache data.
- cache the first search result after deduplication to the first-level cache space to obtain the first-level cache data including:
- the sorted first search results are cached in the first-level cache space.
- calculate the capacity of caching the first-level cache data including:
- the capacity of caching the first-level cache data is calculated according to the capacity of the first-level cache space and the capacity of the first search result; the capacity of the first-level cache data is proportional to the capacity of the first-level cache space; so The capacity of the first-level cache data is inversely proportional to the capacity of the first search result.
- the capacity of the first-level cache data is adjusted in real time and adaptively to avoid the waste of computer resources and improve the efficiency of data retrieval.
- the first-level cache data after obtaining the first-level cache data, it also includes:
- the secondary cache space includes a second condition sequence list; the first request field and the secondary condition sequence list are recorded in the second condition sequence list The mapping relationship of the index; the secondary index is used to index the secondary cache data;
- the method also includes:
- the second-level cache data is adjusted in real time to ensure the consistency of the first-level cache data and the second-level cache data.
- embodiments of the present invention provide a data retrieval device based on cloud computing, including:
- An acquisition module used to obtain a retrieval request; the retrieval request includes a first request field;
- a processing module configured to generate a second request field that satisfies the retrieval conditions based on the first request field; the first request field is different from the second request field; the retrieval conditions are based on data in the cloud database Field generated, indicating the fields in the cloud database that allow indexing data;
- embodiments of the present invention provide a data retrieval system based on cloud computing, a scheduling service and multiple retrieval engines; the retrieval conditions of the multiple retrieval engines are different; for any retrieval engine, the retrieval conditions of the retrieval engine are The search conditions are generated based on the fields of data in the cloud database connected to the search engine, indicating the fields in the cloud database that allow indexing data;
- the scheduling service is used to obtain a retrieval request and send the retrieval request to a retrieval engine; the retrieval request includes a first request field;
- the retrieval engine is configured to generate a second request field that satisfies the retrieval conditions of the retrieval engine based on the first request field; the first request field is different from the second request field. ;
- the retrieval engine retrieves data from the cloud database according to the second request field and obtains the first retrieval result.
- an embodiment of the present invention further provides a computer device, including:
- Memory used to store program instructions
- a processor configured to call program instructions stored in the memory, and execute the above cloud computing-based data retrieval method according to the obtained program.
- embodiments of the present invention further provide a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to cause the computer to perform the above-mentioned cloud computing-based data retrieval. method.
- Figure 1 is a schematic architectural diagram of a cloud computing-based data retrieval system provided by an embodiment of the present invention
- Figure 2 is a schematic flow chart of a cloud computing-based data retrieval method provided by an embodiment of the present invention
- Figure 3 is a schematic structural diagram of a search engine provided by an embodiment of the present invention.
- Figure 4 is a schematic structural diagram of a data retrieval device based on cloud computing provided by an embodiment of the present invention.
- Figure 1 exemplarily shows an architectural diagram of a cloud computing-based data retrieval system applicable to the embodiment of the present invention.
- the system architecture includes a scheduling service 110 and a retrieval engine 120.
- the scheduling service 110 is used to obtain a retrieval request and send the retrieval request to the retrieval engine 120; wherein the retrieval request includes a first request field.
- the scheduling service obtains retrieval requests sent by users through API (Application Programming Interface).
- the request field indicates the fields that need to be retrieved, such as height, weight, order number and other fields.
- the request field can include multiple fields, such as three fields a, b, and c.
- the retrieval engine 120 includes multiple retrieval engines; for example, it includes retrieval engine j1, retrieval engine j2,..., retrieval engine jn; where n represents the number of retrieval engines.
- the search engine is connected to the cloud database and used to retrieve data from the cloud database.
- the cloud database corresponds to the search engine, for example, the cloud database s1 is connected to the search engine j1; however, the cloud database s1 can include multiple databases, which is not limited here.
- search conditions are set. Therefore, after obtaining the first request field, the search engine first determines whether the first request field satisfies the search conditions. If not, it generates a second request field that satisfies the search conditions based on the first request field. For example, there are three fields in the first request: a, b, and c; among them, the data in the cloud database connected to the search engine does not have the c field, so it means that the c field does not meet the search conditions of the search engine. Then, based on the first request field, a second request field that satisfies the search conditions will be generated; the second request field only includes two fields, a and b.
- the search engine After generating the second request field, the search engine retrieves data from the cloud database based on the second request field and obtains the first search result.
- the retrieval engine is configured to integrate the first retrieval results retrieved by each retrieval engine to obtain cached data after the retrieval engine retrieves the first retrieval result. Cached data is used for secondary retrieval by users.
- FIG. 1 is only an example, and the embodiment of the present invention is not limited thereto.
- FIG. 2 exemplarily shows a schematic flowchart of a cloud computing-based data retrieval method provided by an embodiment of the present invention. This process can be executed by a cloud computing-based data retrieval device.
- the process specifically includes:
- Step 210 Obtain the retrieval request.
- the retrieval request includes the first request field.
- the retrieval request is sent by the user, and the scheduling service receives the retrieval request and sends the retrieval request to each retrieval engine.
- the user sends a retrieval request to the scheduling service through UI (User Interface) or CLI (command-line interface).
- the first request field of the retrieval request may include multiple fields; for example, it includes four fields: a, b, c, and d, which are respectively a province area field, a city area field, a county area field, and a town area field.
- the search request indicates retrieving the population of town d in province a, city b, county c, and county c.
- Step 220 Generate a second request field that satisfies the search condition based on the first request field.
- the first request field and the second request field are different; the search conditions are generated based on the fields of the data in the cloud database, indicating the fields in the cloud database that allow indexing data.
- cloud database s1 stores data in the form of "key-value”.
- the primary key "key” includes three fields: a, b, and c. This means that cloud database s1 allows the fields of index data to be a, b, and c.
- the search condition of search engine j1 is: the requested field is within the range of the three fields a, b, and c.
- search engine j1 is connected to cloud database s1; the data record of cloud database s1 includes the population of province a, city b, county c, but does not include the population of towns and areas under county c.
- the search conditions of search engine j1 can only query the three fields a, b, and c. Therefore, the retrieval engine j1 generates a second request field that satisfies the retrieval conditions of the retrieval engine based on the first request field and the retrieval conditions. That is, the second request field includes three fields: a, b, and c.
- the first request field satisfies the search conditions of each search engine, then the first request field is directly used as the second request field.
- Step 230 retrieve data from the cloud database according to the second request field to obtain the first search result.
- Figure 3 is a schematic structural diagram of a retrieval engine exemplarily shown in this application.
- the retrieval engine includes a retrieval dispatch module, a retrieval management module, a cache management module, and a cache retrieval module; wherein the retrieval dispatch module is used to Based on the first request field, generate a second request field that satisfies the search conditions of the search engine according to the search conditions; the retrieval management module is used to retrieve data from the cloud database according to the second request field, and add the first search result to the first-level cache space ;
- the cache retrieval module is used to retrieve data from the first-level cache data according to the first request field, and cache the second search results to the second-level cache space; the cache management module is used to feed back the second-level cache data, and adjust the first-level cache data in real time and second-level cache data.
- the search engine caches the first search result into the first-level cache space to obtain the first-level cache data; wherein the first-level cache space includes the first condition sequence list; the first request field and a first condition sequence list are recorded in the first level cache space.
- the mapping relationship of the first-level index; the first-level index is used to index the first-level cache data.
- mapping relationship between the first request field and the primary index is as shown in Table 1 below:
- mapping relationship between the first-level index and the first-level cache data is shown in Table 2 below:
- the first request field is an ordered field sequence organized based on element fields.
- the core attributes of the conditional feature are the unique ID, type, and supported operators of the feature field.
- each condition field is sorted by the value of the unique ID of the feature field and then spliced together.
- the mapping relationship between each field and the first-level index is stored in the first-level cache space.
- the first request field includes multiple fields; the search engine is also configured to sort and group the multiple fields; and sort the first search results according to the sorting and grouping of the multiple fields.
- conditional cleaning refers to converting complex various forms of natural language search fields into standard search fields of the search engine; for example, the natural language search field is "body weight loss” and is converted into the standard search field of the search engine as "weight”. ,BMI index” and other fields.
- the cleaning process includes field coding, field sorting, and field grouping; among them, conditional coding is achieved by matching the request field input by the user with the unique ID of the element field in the standard field. Each condition field will be matched to a unique element field.
- Field sorting refers to sorting from small to large in numerical order of feature field IDs according to the definition of feature fields.
- Field grouping refers to incorporating standard retrieval fields into different memory groups according to business domain planning to achieve grouping of first-level cache data.
- the retrieval engine is also used to query the capacity of the first-level cache space and the capacity of the first retrieval result; and calculate the capacity of caching the first-level cache data based on the capacity of the first-level cache space and the capacity of the first retrieval result. ;
- the capacity of the first-level cache data is directly proportional to the capacity of the first-level cache space; the capacity of the first-level cache data is inversely proportional to the capacity of the first search result.
- the cache expansion rate index control is adaptively realized and the management of the cache space is realized.
- temporarily unused first-level cache data can be placed into a high-speed disk array as temporary swap space, which is not specifically limited here.
- the restriction on the result set in the search conditions is combined with the cache margin to amplify it by 5-10 times, and then the search instructions are sent to the search engine.
- the specific amplification ratio adopts the ratio of the margin to the total capacity, linear amplification, up to 10 times or other multiples, and is not specifically limited here.
- the search engine After querying the first-level cache data, the search engine will retrieve data from the first-level cache data according to the first request field to obtain the second search result; cache the second search result to the second-level cache space to obtain the second-level cache data;
- the secondary cache space includes a second condition sequence list; the second condition sequence list records the mapping relationship between the first request field and the secondary index; the secondary index is used to index the secondary cache data, and finally feeds back the secondary cache data , for users to view.
- mapping relationship between the first request field and the secondary index is as shown in Table 3 below:
- mapping relationship between the secondary index and the secondary cache data is shown in Table 2 below:
- the primary key and the first-level cache data are standard field sequences.
- the difference from the first-level cache is that the corresponding value is the index value of the first search result.
- the index is used to query the real data in the first search result.
- the secondary cache data supports two types of retrieval, namely: conventional hash retrieval and fuzzy matching, sorting, and grouping retrieval.
- conventional hash retrieval it is obtained directly from the hash table through two calculations.
- retrieval that includes fuzzy matching, sorting, and grouping the first-level cache data is processed according to corresponding processing requirements by extending special retrieval implementation logic in the retrieval engine to obtain it.
- the retrieval engine is also configured to receive an elimination instruction for the first-level cache data; wherein the elimination instruction is sent after the first-level cache data is modified;
- the retrieval engine will delete the L2 cache data corresponding to the elimination instruction from the L2 cache space.
- embodiments of the present invention provide a two-way feedback mechanism; two-way feedback means that the second-level cache data, on the one hand, receives the requirements of the first-level cache data regarding the elimination of cache data, and on the other hand, it reports its own hit rate. Feed back data to the first level cache. This ensures the consistency of the first-level cache data and the second-level cache data. Among them, the hit rate indicates the hit rate of users viewing the second-level cache data.
- the secondary cache data will be forcibly invalidated.
- the granularity of invalidation processing of the second-level cache data can be set by the device, which can distinguish table-level, record-level, field and update. When data that meets the conditions is updated, the corresponding second-level cache data will be eliminated.
- the first-level cache data that misses within a preset period is deleted from the first-level cache space. That is to say, the first-level cache space is released, thereby reducing the consumption of computing resources.
- the search engine also queries the homogeneous data in the first search results of multiple search engines based on the cloud native traffic transfer records; and then combines the homogeneous data in the first search results of multiple search engines.
- the data is cached to the first-level cache space after deduplication.
- homogeneous data means exactly the same data. Because the integrated architecture of the cloud environment brings about the problem of homogeneous data, the most typical disaster recovery system data and the main center data are exactly the same.
- different downstream application nodes may store essentially the same data content. Specifically, all disaster recovery node traffic is transferred to the main central node. All downstream application node traffic is transferred to the upstream application node (source node).
- the homogeneous data from the upstream application node and the downstream node can be queried through the traffic transfer record, and the homogeneous data from the downstream node can be deleted to achieve the deduplication effect.
- FIG. 4 exemplarily shows a structural schematic diagram of a cloud computing-based data retrieval device provided by an embodiment of the present invention.
- the device can execute the process of a cloud computing-based data retrieval method.
- the device specifically includes:
- Obtain module 410 used to obtain a retrieval request; the retrieval request includes a first request field;
- the processing module 420 is configured to generate a second request field that satisfies the retrieval condition according to the first request field; the first request field is different from the second request field; the retrieval condition is based on data in the cloud database Generated by fields, indicating the fields in the cloud database that allow indexing data;
- processing module 420 is also used to:
- the first level cache space After deduplicating the homogeneous data in the first search result, cache the deduplicated first search result to the first level cache space to obtain the first level cache data; the first level cache space includes a first condition sequence list ; The first condition sequence list records the mapping relationship between the first request field and the first-level index; the first-level index is used to index the first-level cache data.
- the first request field includes multiple fields
- the processing module 420 is specifically used to:
- the sorted first search results are cached in the first-level cache space.
- processing module 420 is specifically used to:
- the capacity of caching the first-level cache data is calculated according to the capacity of the first-level cache space and the capacity of the first search result; the capacity of the first-level cache data is proportional to the capacity of the first-level cache space; so The capacity of the first-level cache data is inversely proportional to the capacity of the first search result.
- processing module 420 is also used to:
- the secondary cache space includes a second condition sequence list; the first request field and the secondary condition sequence list are recorded in the second condition sequence list The mapping relationship of the index; the secondary index is used to index the secondary cache data;
- processing module 420 is also used to:
- embodiments of the present invention also provide a computer device, including:
- Memory used to store program instructions
- a processor configured to call program instructions stored in the memory, and execute the above cloud computing-based data retrieval method according to the obtained program.
- embodiments of the present invention also provide a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to cause the computer to execute the above cloud computing-based Data retrieval methods.
- embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
- computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
- These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
- the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
- These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
- Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
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)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
本发明公开了一种基于云计算的数据检索方法、装置及系统,包括:获取检索请求;其中,检索请求包括第一请求字段;根据第一请求字段,生成满足检索条件的第二请求字段;其中,第一请求字段与第二请求字段不相同;检索条件是基于云数据库中数据的字段生成的,表示云数据库中允许索引数据的字段;根据第二请求字段从云数据库中检索数据,得到第一检索结果。因为第二请求字段满足检索条件,因此根据第二请求字段从云数据库中检索数据可以保证检索数据的准确性。且不需要在各检索引擎设置检索服务,避免业务逻辑开发,降低业务逻辑开发、维护成本。
Description
相关申请的交叉引用
本申请要求在2022年08月23日提交中国专利局、申请号为202211013674.6、申请名称为“一种基于云计算的数据检索方法、装置及系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本发明涉及数据处理技术领域,尤其涉及一种基于云计算的数据检索方法、装置及系统。
随着网络信息资源的激增,资源种类的丰富,需要存储的数据越来越多。在云计算的概念提出之后,线下存储的数据逐渐转移至线上存储。也就是将数据存储至云数据库。
为了防止用户在检索数据时出现数据孤岛,需要从各云数据库中进行数据检索,进而实现数据整合。目前,从各云数据库从进行数据检索方法一般是将检索请求直接发送至各检索引擎;其中,各检索引擎对接不同的云数据库,且各检索引擎加载有统一化的检索服务。用户在进行数据检索时,在各检索引擎中调用统一化的检索服务从各云数据库检索出数据结果,然后将数据结果进行整合。
然而,因为各企业对数据的管理方式不同,因此对应的各云数据库的数据格式也存在差异,在检索数据时所使用的检索条件也有所差异。若将各云数据源的数据检索方式统一化,则检索数据时所使用的检索条件一致,会导致检索数据时出现错误。且加载统一化的检索服务存在着业务逻辑开发的问题,即业务逻辑开发难度大、维护成本高等问题。
发明内容
本发明实施例提供一种基于云计算的数据检索方法、装置及系统,用于自适应的从各云数据库检索出数据结果,提升检索数据的准确性,且避免业务逻辑再开发,降低业务逻辑开发难度和维护成本。
第一方面,本发明实施例提供一种基于云计算的数据检索方法,包括:
获取检索请求;所述检索请求包括第一请求字段;
根据所述第一请求字段,生成满足检索条件的第二请求字段;所述第一请求字段与所述第二请求字段不相同;所述检索条件是基于云数据库中数据的字段生成的,表示所述云数据库中允许索引数据的字段;
根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
上述技术方案中,基于云计算的数据检索方法应用于数据检索系统,该系统包括调度服务和多个检索引擎;其中,多个检索引擎的检索条件不相同;针对任一检索引擎,检索引擎的检索条件是基于与检索引擎对接的云数据库中数据的字段生成的,表示云数据库中允许索引数据的字段。调度服务用于获取用户发送的检索请求,并在获取检索请求之后,将检索请求发送至各检索引擎,由各检索引擎从对应的云数据库中检索数据。
针对任一检索引擎,该检索引擎预设有检索条件。该检索引擎会根据对应的检索条件,基于第一请求字段生成第二请求字段,第二请求字段满足检索条件,进而根据第二请求字段在云数据库中检索数据时,保证检索数据的准确性。且不需要在各检索引擎设置检索服务,避免业务逻辑的再开发,降低业务逻辑开发难度和维护成本。
可选的,得到第一检索结果之后,还包括:
根据云原生流量转移记录,查询出所述第一检索结果中的同质数据;
将所述第一检索结果中的同质数据去重后,将去重后的第一检索结果缓存至一级缓存空间,得到一级缓存数据;所述一级缓存空间包括第一条件序列表;所述第一条件序列表中记录有第一请求字段与一级索引的映射关系;所述一级索引用于索引所述一级缓存数据。
上述技术方案中,通过对同质数据的去重,避免检索结果中存在相同的数据,提升数据检索的准确性。
可选的,将去重后的第一检索结果缓存至一级缓存空间,得到一级缓存数据,包括:
计算缓存所述一级缓存数据的容量;
对所述第一请求字段中的各字段进行排序和分组;
根据所述各字段的排序和分组对去重后的第一检索结果进行排序;
基于缓存所述一级缓存数据的容量,将排序后的第一检索结果缓存至一级缓存空间。
可选的,计算缓存所述一级缓存数据的容量,包括:
查询所述一级缓存空间的容量和所述第一检索结果的容量;
根据所述一级缓存空间的容量和所述第一检索结果的容量计算缓存所述一级缓存数据的容量;所述一级缓存数据的容量与所述一级缓存空间的容量成正比;所述一级缓存数据的容量与所述第一检索结果的容量成反比。
上述技术方案中,实时的、自适应的调整一级缓存数据的容量,避免计算机资源的浪费,提高数据检索效率。
可选的,得到一级缓存数据之后,还包括:
根据所述第一请求字段从所述一级缓存数据中检索数据,得到第二检索结果;
将所述第二检索结果缓存至二级缓存空间,得到二级缓存数据;所述二级缓存空间包括第二条件序列表;所述第二条件序列表中记录有第一请求字段与二级索引的映射关系;所述二级索引用于索引所述二级缓存数据;
反馈所述二级缓存数据。
可选的,所述方法还包括:
接收针对一级缓存数据的淘汰指令;所述淘汰指令是所述一级缓存数据发生修改后发送的;
将所述淘汰指令对应的二级缓存数据从二级缓存空间删除;
将预设周期内未命中的一级缓存数据从一级缓存空间删除。
上述技术方案中,实时的调整二级缓存数据,保证一级缓存数据和二级缓存数据的一致性。通过将预设周期内未命中的一级缓存数据从一级缓存空间删除,来避免计算机资源的浪费。
第二方面,本发明实施例提供一种基于云计算的数据检索装置,包括:
获取模块,用于获取检索请求;所述检索请求包括第一请求字段;
处理模块,用于根据所述第一请求字段,生成满足检索条件的第二请求字段;所述第一请求字段与所述第二请求字段不相同;所述检索条件是基于云数据库中数据的字段生成的,表示所述云数据库中允许索引数据的字段;
根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
第三方面,本发明实施例提供一种基于云计算的数据检索系统,调度服务和多个检索引擎;所述多个检索引擎的检索条件不相同;针对任一检索引擎,所述检索引擎的所述检索条件是基于与所述检索引擎对接的云数据库中数据的字段生成的,表示所述云数据库中允许索引数据的字段;
所述调度服务用于获取检索请求,将所述检索请求发送至检索引擎;所述检索请求包括第一请求字段;
针对任一检索引擎,所述检索引擎用于根据所述第一请求字段,生成满足所述检索引擎的检索条件的第二请求字段;所述第一请求字段与所述第二请求字段不相同;
所述检索引擎根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
第四方面,本发明实施例还提供一种计算机设备,包括:
存储器,用于存储程序指令;
处理器,用于调用所述存储器中存储的程序指令,按照获得的程序执行上述基于云计算的数据检索方法。
第五方面,本发明实施例还提供一种计算机可读存储介质,所述计算机可读存储介质存储有计算机可执行指令,所述计算机可执行指令用于使计算 机执行上述基于云计算的数据检索方法。
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简要介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域的普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种基于云计算的数据检索系统的架构示意图;
图2为本发明实施例提供的一种基于云计算的数据检索方法的流程示意图;
图3为本发明实施例提供的一种检索引擎的结构示意图;
图4为本发明实施例提供的一种基于云计算的数据检索装置的结构示意图。
为了使本发明的目的、技术方案和优点更加清楚,下面将结合附图对本发明作进一步地详细描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本发明保护的范围。
图1示例性的示出了本发明实施例所适用的一种基于云计算的数据检索系统的架构示意图,该系统架构包括调度服务110和检索引擎120。
其中,调度服务110,用于获取检索请求,将所述检索请求发送至检索引擎120;其中,检索请求包括第一请求字段。如调度服务通过API(Application Programming Interface,应用程序编程接口)获取用户发送检索请求。请求字段表示需要进行检索的字段,如身高、体重、订单号等字段。请求字段可以 包括多个字段,如包括a、b、c三个字段。
检索引擎120包括多个检索引擎;如包括检索引擎j1、检索引擎j2、……、检索引擎jn;其中,n表示检索引擎的数量。检索引擎与云数据库对接,用于从云数据库中检索数据。对应的,云数据库与检索引擎是相对应的,如云数据库s1与检索引擎j1对接;但是云数据库s1可以包括多个数据库,在此不进行限定。
针对任一检索引擎,设置有检索条件。因此该检索引擎得到第一请求字段之后,先判断第一请求字段是否满足检索条件,若不满足,则基于第一请求字段,生成满足检索条件的第二请求字段。例如,第一请求字段a、b、c三个字段;其中检索引擎对接的云数据库中的数据不具备c字段,因此表示c字段不满足检索引擎的检索条件。然后将基于第一请求字段,生成满足检索条件的第二请求字段;第二请求字段仅包括a、b两个字段。
检索引擎在生成第二请求字段之后,根据第二请求字段从云数据库中检索数据,得到第一检索结果。
检索引擎用于在检索引擎检索出第一检索结果之后,对各检索引擎检索出的第一检索结果进行整合,得到缓存数据。缓存数据用于供用户进行二次检索。
需要说明的是,上述图1所示的结构仅是一种示例,本发明实施例对此不做限定。
基于上述描述,图2示例性的示出了本发明实施例提供的一种基于云计算的数据检索方法的流程示意图,该流程可由基于云计算的数据检索装置执行。
如图2所示,该流程具体包括:
步骤210,获取检索请求。
其中,检索请求包括第一请求字段。检索请求是用户发送的,由调度服务接收检索请求,并将检索请求发送至各检索引擎。例如,用户通过UI(User Interface,用户界面)或CLI(command-line interface,指命令行界面)向调 度服务发送检索请求。其中,检索请求的第一请求字段可以包括多个字段;如包括a、b、c、d四个字段,分别为省地区字段、市地区字段、县地区字段和镇地区字段。检索请求表示检索a省份b市c县d镇的人口数量。
步骤220,根据所述第一请求字段,生成满足检索条件的第二请求字段。
其中,第一请求字段与第二请求字段不相同;检索条件是基于云数据库中数据的字段生成的,表示云数据库中允许索引数据的字段。例如,云数据库s1以“key-value”形式存储数据,主键“key”包括a、b、c三个字段。则表示云数据库s1允许索引数据的字段为a、b、c三个字段。换句话说,检索引擎j1的检索条件是:请求字段在a、b、c三个字段的范围内。
在一些可实施的方式中,各检索引擎的检索条件不同,且第一请求字段不满足各检索引擎的检索条件。例如,检索引擎j1对接云数据库s1;云数据库s1的数据记录有a省份b市c县的人口数量,不包括c县下的各镇地区的人口数量。
也就是说,检索引擎j1的检索条件只能查询a、b、c三个字段。因此,检索引擎j1基于第一请求字段,根据检索条件生成满足所述检索引擎的检索条件的第二请求字段,即第二请求字段包括a、b、c三个字段。
在一些可实施的方式中,第一请求字段满足各检索引擎的检索条件,则直接将第一请求字段作为第二请求字段。
步骤230,根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
图3为本申请示例性示出的一种检索引擎的结构示意图,如图3所示,检索引擎包括检索派发模块、检索管理模块、缓存管理模块、缓存检索模块;其中,检索派发模块用于基于第一请求字段,根据检索条件生成满足检索引擎的检索条件的第二请求字段;检索管理模块用于根据第二请求字段从云数据库中检索数据,并将第一检索结果加入一级缓存空间;缓存检索模块用于根据第一请求字段从一级缓存数据中检索数据,将第二检索结果缓存至二级缓存空间;缓存管理模块用于反馈二级缓存数据,以及实时调整一级缓存数 据和二级缓存数据。
具体的,检索引擎将第一检索结果缓存至一级缓存空间,得到一级缓存数据;其中,一级缓存空间包括第一条件序列表;第一条件序列表中记录有第一请求字段与一级索引的映射关系;一级索引用于索引一级缓存数据。
第一请求字段与一级索引的映射关系如下述表1所示:
表1
| 第一请求字段 | 一级索引 |
| cond_1 | index_1 |
| cond_2 | index_2 |
| …… | …… |
| cond_m | index_m |
一级索引与一级缓存数据的映射关系如下述表2所示:
表2
| 一级索引 | 一级缓存数据 |
| index_1 | data_1 |
| index_2 | data_2 |
| …… | …… |
| index_m | data_m |
其中,第一请求字段以要素字段为基础组织形成的有序字段序列。其中条件要素的核心属性即要素字段的唯一ID,类型,和支持的运算符。组装过程以要素字段唯一ID的取值大小排序后拼接各条件字段。每一个字段与一级索引的映射关系存入一级缓存空间中。
在一些可实施的方式中,第一请求字段包括多个字段;检索引擎还用于对多个字段进行排序和分组;根据多个字段的排序和分组对第一检索结果进行排序。
也就是说,检索引擎还用于对第一请求字段进行条件清洗。其中,条件清洗指的是将复杂的各类形式的自然语言检索字段转换为检索引擎的标准检 索字段;例如,自然语言检索字段为“体型消瘦”,转换为检索引擎的标准检索字段为“重量、BMI指数”等字段。
清洗过程包括对字段编码、字段排序、字段分组;其中,条件编码是指通过将用户输入的请求字段与标准字段中要素字段唯一ID匹配实现,每一个条件字段将匹配到唯一的要素字段。
字段排序是指依照要素字段的定义,按要素字段ID的数值顺序从小到大排序。
字段分组是指将标准的检索字段按照业务域规划纳入不同的内存组,以实现对一级缓存数据分组。
在一些实施例中,所述检索引擎还用于查询一级缓存空间的容量和第一检索结果的容量;根据一级缓存空间的容量和第一检索结果的容量计算缓存一级缓存数据的容量;一级缓存数据的容量与一级缓存空间的容量成正比;一级缓存数据的容量与第一检索结果的容量成反比。
通过上述技术方案,自适应的实现对缓存膨胀率指数控制,实现对缓存空间的管理。在一些实施例中,可以通过将暂时不使用的一级缓存数据放入高速磁盘阵列作为临时交换空间,具体在此不做限定。
例如,将检索条件中对结果集的限定结合缓存余量放大5-10倍后将检索指令派发给检索引擎。具体的放大比例采用余量占总容量的比例,线性放大,最大为10倍或其他倍数,在此不作具体限定。
在查询出一级缓存数据之后,检索引擎会根据第一请求字段从一级缓存数据中检索数据,得到第二检索结果;将第二检索结果缓存至二级缓存空间,得到二级缓存数据;其中,二级缓存空间包括第二条件序列表;第二条件序列表中记录有第一请求字段与二级索引的映射关系;二级索引用于索引二级缓存数据,最后反馈二级缓存数据,供用户查看。
第一请求字段与二级索引的映射关系如下述表3所示:
表3
| 第一请求字段 | 二级索引 |
| cond_1 | rsindex_1 |
| cond_2 | rsindex_2 |
| …… | …… |
| cond_m | rsindex_m |
二级索引与二级缓存数据的映射关系如下述表2所示:
表4
| 二级索引 | 二级缓存数据 |
| rsindex_1 | r_data_1 |
| rsindex_2 | r_data_2 |
| …… | …… |
| rsindex_m | r_data_m |
其中,主键与一级缓存数据是标准的字段序列,与一级缓存的区别是其对应的值则是第一检索结果的索引值。索引用于在第一检索结果中查询真实的数据。
在本发明实施例中,二级缓存数据支持两类检索,分别是:常规哈希检索和模糊匹配、排序、分组的检索。对于常规哈希检索直接在哈希表通过两次计算获取。对于包含模糊匹配、排序、分组的检索,通过在检索引擎中扩展特殊检索实现逻辑的方式对一级缓存数据按相应的处理要求处理后获取。
在一些实施例中,检索引擎还用于接收针对一级缓存数据的淘汰指令;其中,淘汰指令是一级缓存数据发生修改后发送的;
检索引擎将淘汰指令对应的二级缓存数据从二级缓存空间删除。
也就是说,针对二级缓存数据,本发明实施例提供了双向反馈的机制;双向反馈是指二级缓存数据一方面接收一级缓存数据关于缓存数据淘汰的要求,一方面将自身命中率情况反馈给一级缓存数据。以此保证一级缓存数据和二级缓存数据的一致性。其中,命中率表示用户查看二级缓存数据的命中 率。
由于一级缓存数据在命中率响应上相比二级缓存数据存在逻辑上的延迟。因此在二级缓存数据未命中数据时主动探测一级缓存的数据可用性,提升的查询数据的准确性。例如,一级缓存数据中某一数据参数由“1”变为了“2”,因为二级缓存数据是从一级缓存数据中检索得到的,假设该数据为二级缓存数据,此时二级缓存数据与一级缓存数据不再一致。因此,为了保证数据一致性,将对二级缓存数据做强制失效处理。
另外,二级缓存数据的失效处理粒度可通过装置设定,可区分表级、记录级、字段及的更新,当满足条件的数据发生更新时,淘汰对应的二级缓存数据。
在一些实施例中,将预设周期内未命中的一级缓存数据从一级缓存空间删除。也就是释放一级缓存空间,从而减少计算资源的消耗。
例如,在3s(预设周期内)用户并未查看某一部分的一级缓存数据,则将该部分的一级缓存数据从一级缓存空间删除。
在一些可实施的方式中,检索引擎还根据云原生流量转移记录,查询出多个检索引擎的第一检索结果中的同质数据;然后将多个检索引擎的第一检索结果中的同质数据去重后缓存至一级缓存空间。
其中,同质数据表示完全相同的数据。因为云环境一体化架构带来了同质数据问题,最典型的灾备系统数据和主中心数据是完全相同的。此外,不同的下游应用节点(非源头节点)可能存储了本质相同的数据内容。具体的,将灾备节点流量全部转移到主中心节点。下游应用节点流量全部转移到上游应用节点(源头节点)中。
因此,可以通过流量转移记录查询出来自上游应用节点和下游节点的同质数据,将下游节点的同质数据删除,以此实现去重的效果。
基于相同的技术构思,图4示例性的示出了本发明实施例提供的一种基于云计算的数据检索装置的结构示意图,该装置可以执行基于云计算的数据检索方法的流程。
如图4所示,该装置具体包括:
获取模块410,用于获取检索请求;所述检索请求包括第一请求字段;
处理模块420,用于根据所述第一请求字段,生成满足检索条件的第二请求字段;所述第一请求字段与所述第二请求字段不相同;所述检索条件是基于云数据库中数据的字段生成的,表示所述云数据库中允许索引数据的字段;
根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
可选的,所述处理模块420还用于:
得到第一检索结果之后,根据云原生流量转移记录,查询出所述第一检索结果中的同质数据;
将所述第一检索结果中的同质数据去重后,将去重后的第一检索结果缓存至一级缓存空间,得到一级缓存数据;所述一级缓存空间包括第一条件序列表;所述第一条件序列表中记录有第一请求字段与一级索引的映射关系;所述一级索引用于索引所述一级缓存数据。
可选的,所述第一请求字段包括多个字段;
所述处理模块420具体用于:
计算缓存所述一级缓存数据的容量;
对所述第一请求字段中的各字段进行排序和分组;
根据所述各字段的排序和分组对去重后的第一检索结果进行排序;
基于缓存所述一级缓存数据的容量,将排序后的第一检索结果缓存至一级缓存空间。
可选的,所述处理模块420具体用于:
查询所述一级缓存空间的容量和所述第一检索结果的容量;
根据所述一级缓存空间的容量和所述第一检索结果的容量计算缓存所述一级缓存数据的容量;所述一级缓存数据的容量与所述一级缓存空间的容量成正比;所述一级缓存数据的容量与所述第一检索结果的容量成反比。
可选的,所述处理模块420还用于:
得到一级缓存数据之后,根据所述第一请求字段从所述一级缓存数据中 检索数据,得到第二检索结果;
将所述第二检索结果缓存至二级缓存空间,得到二级缓存数据;所述二级缓存空间包括第二条件序列表;所述第二条件序列表中记录有第一请求字段与二级索引的映射关系;所述二级索引用于索引所述二级缓存数据;
反馈所述二级缓存数据。
可选的,所述处理模块420还用于:
接收针对所述一级缓存数据的淘汰指令;所述淘汰指令是所述一级缓存数据发生修改后发送的;
将所述淘汰指令对应的二级缓存数据从所述二级缓存空间删除;
将预设周期内未命中的一级缓存数据从一级缓存空间删除。
基于相同的技术构思,本发明实施例还提供一种计算机设备,包括:
存储器,用于存储程序指令;
处理器,用于调用所述存储器中存储的程序指令,按照获得的程序执行上述基于云计算的数据检索方法。
基于相同的技术构思,本发明实施例还提供一种计算机可读存储介质,所述计算机可读存储介质存储有计算机可执行指令,所述计算机可执行指令用于使计算机执行上述基于云计算的数据检索方法。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计 算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
Claims (10)
- 一种基于云计算的数据检索方法,其特征在于,包括:获取检索请求;所述检索请求包括第一请求字段;根据所述第一请求字段,生成满足检索条件的第二请求字段;所述第一请求字段与所述第二请求字段不相同;所述检索条件是基于云数据库中数据的字段生成的,表示所述云数据库中允许索引数据的字段;根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
- 如权利要求1所述的方法,其特征在于,得到第一检索结果之后,还包括:根据云原生流量转移记录,查询出所述第一检索结果中的同质数据;将所述第一检索结果中的同质数据去重后,将去重后的第一检索结果缓存至一级缓存空间,得到一级缓存数据;所述一级缓存空间包括第一条件序列表;所述第一条件序列表中记录有第一请求字段与一级索引的映射关系;所述一级索引用于索引所述一级缓存数据。
- 如权利要求2所述的方法,其特征在于,将去重后的第一检索结果缓存至一级缓存空间,得到一级缓存数据,包括:计算缓存所述一级缓存数据的容量;对所述第一请求字段中的各字段进行排序和分组;根据所述各字段的排序和分组对去重后的第一检索结果进行排序;基于缓存所述一级缓存数据的容量,将排序后的第一检索结果缓存至一级缓存空间。
- 如权利要求3所述的方法,其特征在于,计算缓存所述一级缓存数据的容量,包括:查询所述一级缓存空间的容量和所述第一检索结果的容量;根据所述一级缓存空间的容量和所述第一检索结果的容量计算缓存所述一级缓存数据的容量;所述一级缓存数据的容量与所述一级缓存空间的容量 成正比;所述一级缓存数据的容量与所述第一检索结果的容量成反比。
- 如权利要求3所述的方法,其特征在于,得到一级缓存数据之后,还包括:根据所述第一请求字段从所述一级缓存数据中检索数据,得到第二检索结果;将所述第二检索结果缓存至二级缓存空间,得到二级缓存数据;所述二级缓存空间包括第二条件序列表;所述第二条件序列表中记录有第一请求字段与二级索引的映射关系;所述二级索引用于索引所述二级缓存数据;反馈所述二级缓存数据。
- 如权利要求1至5任一项所述的方法,其特征在于,所述方法还包括:接收针对一级缓存数据的淘汰指令;所述淘汰指令是所述一级缓存数据发生修改后发送的;将所述淘汰指令对应的二级缓存数据从二级缓存空间删除;将预设周期内未命中的一级缓存数据从一级缓存空间删除。
- 一种基于云计算的数据检索装置,其特征在于,包括:获取模块,用于获取检索请求;所述检索请求包括第一请求字段;处理模块,用于根据所述第一请求字段,生成满足检索条件的第二请求字段;所述第一请求字段与所述第二请求字段不相同;所述检索条件是基于云数据库中数据的字段生成的,表示所述云数据库中允许索引数据的字段;根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
- 一种基于云计算的数据检索系统,其特征在于,包括:调度服务和多个检索引擎;所述多个检索引擎的检索条件不相同;针对任一检索引擎,所述检索引擎的所述检索条件是基于与所述检索引擎对接的云数据库中数据的字段生成的,表示所述云数据库中允许索引数据的字段;所述调度服务用于获取检索请求,将所述检索请求发送至检索引擎;所述检索请求包括第一请求字段;针对任一检索引擎,所述检索引擎用于根据所述第一请求字段,生成满 足所述检索引擎的检索条件的第二请求字段;所述第一请求字段与所述第二请求字段不相同;所述检索引擎根据所述第二请求字段从云数据库中检索数据,得到第一检索结果。
- 一种计算机设备,其特征在于,包括:存储器,用于存储程序指令;处理器,用于调用所述存储器中存储的程序指令,按照获得的程序执行权利要求1至6任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储有计算机可执行指令,所述计算机可执行指令用于使计算机执行权利要求1至6任一项所述的方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211013674.6 | 2022-08-23 | ||
| CN202211013674.6A CN115438032A (zh) | 2022-08-23 | 2022-08-23 | 一种基于云计算的数据检索方法、装置及系统 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024040784A1 true WO2024040784A1 (zh) | 2024-02-29 |
Family
ID=84244164
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/135924 Ceased WO2024040784A1 (zh) | 2022-08-23 | 2022-12-01 | 一种基于云计算的数据检索方法、装置及系统 |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN115438032A (zh) |
| TW (1) | TWI877584B (zh) |
| WO (1) | WO2024040784A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118132598A (zh) * | 2024-05-07 | 2024-06-04 | 深圳九有数据库有限公司 | 基于多级缓存的数据库数据处理方法及设备 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190303481A1 (en) * | 2018-03-30 | 2019-10-03 | International Business Machines Corporation | Supporting a join operation against multiple nosql databases |
| CN111309760A (zh) * | 2020-02-10 | 2020-06-19 | 江苏满运软件科技有限公司 | 数据检索方法、系统、设备及存储介质 |
| US20200226116A1 (en) * | 2019-01-16 | 2020-07-16 | Syscom Computer Engineering Co. | Fast index creation system for cloud big data database |
| CN114625798A (zh) * | 2020-12-14 | 2022-06-14 | 金篆信科有限责任公司 | 数据检索方法、装置、电子设备及存储介质 |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2839168B1 (fr) * | 2002-04-25 | 2006-03-24 | Commissariat Energie Atomique | Procede et systeme d'extraction automatique d'informations contenues dans une base de donnees et d'enrichissement automatique du contenu de cette base de donnees |
| CN103314371B (zh) * | 2010-12-31 | 2017-12-15 | 肖岩 | 一种检索的方法和系统 |
| CN103412916B (zh) * | 2013-08-07 | 2016-08-10 | 北京京东尚科信息技术有限公司 | 一种监控系统的多维度数据存储、检索方法及装置 |
| TWI526857B (zh) * | 2014-11-06 | 2016-03-21 | The database acceleration method is used to calculate the index value and the hybrid layer cache | |
| US11074250B2 (en) * | 2017-06-27 | 2021-07-27 | OWOX Limted | Technologies for implementing ontological models for natural language queries |
| CN112352230B (zh) * | 2018-06-28 | 2021-08-27 | 三菱电机株式会社 | 检索装置、检索方法及机器学习装置 |
| TWI693525B (zh) * | 2018-12-21 | 2020-05-11 | 凌群電腦股份有限公司 | 雲端大數據資料庫快捷建立索引系統 |
| US11210288B2 (en) * | 2020-05-12 | 2021-12-28 | Coupang Corp. | Systems and methods for reducing database query latency |
| US11016980B1 (en) * | 2020-11-20 | 2021-05-25 | Coupang Corp. | Systems and method for generating search terms |
| US20220215452A1 (en) * | 2021-01-05 | 2022-07-07 | Coupang Corp. | Systems and method for generating machine searchable keywords |
| TWM630236U (zh) * | 2022-03-15 | 2022-08-01 | 時光科技有限公司 | 可編輯資料關聯的資料庫系統 |
-
2022
- 2022-08-23 CN CN202211013674.6A patent/CN115438032A/zh active Pending
- 2022-12-01 WO PCT/CN2022/135924 patent/WO2024040784A1/zh not_active Ceased
-
2023
- 2023-03-16 TW TW112109751A patent/TWI877584B/zh active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190303481A1 (en) * | 2018-03-30 | 2019-10-03 | International Business Machines Corporation | Supporting a join operation against multiple nosql databases |
| US20200226116A1 (en) * | 2019-01-16 | 2020-07-16 | Syscom Computer Engineering Co. | Fast index creation system for cloud big data database |
| CN111309760A (zh) * | 2020-02-10 | 2020-06-19 | 江苏满运软件科技有限公司 | 数据检索方法、系统、设备及存储介质 |
| CN114625798A (zh) * | 2020-12-14 | 2022-06-14 | 金篆信科有限责任公司 | 数据检索方法、装置、电子设备及存储介质 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118132598A (zh) * | 2024-05-07 | 2024-06-04 | 深圳九有数据库有限公司 | 基于多级缓存的数据库数据处理方法及设备 |
Also Published As
| Publication number | Publication date |
|---|---|
| TWI877584B (zh) | 2025-03-21 |
| TW202409853A (zh) | 2024-03-01 |
| CN115438032A (zh) | 2022-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11816126B2 (en) | Large scale unstructured database systems | |
| US11347761B1 (en) | System and methods for distributed database query engines | |
| Auradkar et al. | Data infrastructure at LinkedIn | |
| US10581957B2 (en) | Multi-level data staging for low latency data access | |
| JP6448609B2 (ja) | データ取得方法及びシステム | |
| US10223431B2 (en) | Data stream splitting for low-latency data access | |
| Fernandez et al. | Liquid: Unifying Nearline and Offline Big Data Integration. | |
| CN104781812B (zh) | 策略驱动的数据放置和信息生命周期管理 | |
| CN103631870B (zh) | 一种用于大规模分布式数据处理的系统及其方法 | |
| CN108664516A (zh) | 查询优化方法及相关装置 | |
| CN106599043A (zh) | 用于多级数据库的中间件和多级数据库系统 | |
| CN108874971A (zh) | 一种应用于海量标签化实体数据存储的工具和方法 | |
| WO2014163624A1 (en) | Query integration across databases and file systems | |
| WO2024040784A1 (zh) | 一种基于云计算的数据检索方法、装置及系统 | |
| CN117033322A (zh) | 一种流批一体的大数据存储方法、系统、电子设备及存储介质 | |
| Barkhordari et al. | Atrak: a MapReduce-based data warehouse for big data | |
| CN112434060B (zh) | 数据查询方法及系统 | |
| CN119377258A (zh) | 数据收集与检索分布式系统、方法和计算机设备 | |
| WO2018218504A1 (zh) | 数据查询的方法和装置 | |
| CN115455031B (zh) | 一种Doris的数据查询方法、装置、存储介质及设备 | |
| CN115718571B (zh) | 一种基于多维度特征的数据管理方法和装置 | |
| HK40077130A (zh) | 一种基於云计算的数据检索方法、装置及系统 | |
| CN116414843A (zh) | 一种数据更新方法及装置 | |
| CN115794965B (zh) | 一种数据管理系统及方法 | |
| Maalouf | Performance Optimizations of NoSQL Databases in Distributed Systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22956318 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 22956318 Country of ref document: EP Kind code of ref document: A1 |