CN113297274A - Signed data query method and system - Google Patents
Signed data query method and system Download PDFInfo
- Publication number
- CN113297274A CN113297274A CN202110649208.6A CN202110649208A CN113297274A CN 113297274 A CN113297274 A CN 113297274A CN 202110649208 A CN202110649208 A CN 202110649208A CN 113297274 A CN113297274 A CN 113297274A
- Authority
- CN
- China
- Prior art keywords
- data
- query
- signing
- core form
- elasticsearch
- 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.)
- Granted
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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
-
- 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/23—Updating
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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)
- Computational Linguistics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for inquiring signing data, wherein the method comprises the following steps: acquiring a signing query core form in a PostgreSQL database, and establishing a communication link between the PostgreSQL database and a Kafka cluster; synchronizing the check-in query core form to the Kafka cluster; encapsulating the signing query core form into json data in the Kafka cluster; and synchronizing the json data after encapsulation into an ElasticSearch database, and starting a signing query service. According to the method and the system, an ElasticSearch search engine is adopted, data in a PostgreSQL database is synchronized into the ElasticSearch search engine for signing and service query in a specific format through a Kafka cluster, so that the complex multi-table association and nesting query technology is avoided, and the processing speed and the capability of signing and receiving data can be improved.
Description
Technical Field
The invention relates to the field of big data, in particular to a signed data query method and a signed data query system.
Background
The data query of the four modules of the current signing function module, namely the module to be signed in, the module to be sent out and the module to be signed in, is a real-time query realized based on a PostgreSQL database. Advanced search functions such as dynamic query, fuzzy query and the like provided in the product are realized by carrying out multi-table association, sub-query, left-right matching fuzzy query and the like in a PostgreSQL database. However, the existing technical solutions are complex to implement, SQL needs to be adopted to perform complex operations such as multi-table association, nested query, and the like in the implementation process, huge workload is required for development, and as the traffic volume increases, the performance of SQL is worse, and the user experience is affected.
Disclosure of Invention
One purpose of the present invention is to provide a method and a system for querying signed data, where an ElasticSearch engine is used in the method and the system, and data in a PostgreSQL database is synchronized to the ElasticSearch engine in a specific format through a Kafka cluster for signing and service query, so that the adoption of a complex multi-table association and nested query technology is avoided, and the processing speed and capability of the signed data can be improved.
Another object of the present invention is to provide a method and system for signing data query, which reduces the coupling degree of codes by encapsulating data in a format adapted to an elastic search engine, so that the whole signing query service has higher maintainability and reduces the coordination processing in the code level.
Another object of the present invention is to provide a method and system for querying signed data, which can implement rapid development of query interface due to less code coupling degree, so as to make the service expansion performance better.
The invention also aims to provide a method and a system for inquiring the signed data, wherein the method and the system establish monitoring on the core form of the signed data inquiry, and perform word segmentation on the specified field in the specified core form, so as to be used for fuzzy inquiry of an ElasticSearch search engine, thereby improving the response speed of the signed data inquiry.
In order to achieve at least one of the above objects, the present invention further provides a method for signing a data query, the method comprising the steps of:
acquiring a signing query core form in a PostgreSQL database, and establishing a communication link between the PostgreSQL database and a Kafka cluster;
synchronizing the check-in query core form to the Kafka cluster;
encapsulating the signing query core form into json data in the Kafka cluster;
and synchronizing the json data after encapsulation into an ElasticSearch database, and starting a signing query service.
According to a preferred embodiment of the present invention, the method for synchronizing the check-in query core form includes:
creating an acceptance table query core form topic in the Kafka cluster;
configuring corresponding signing inquiry core form parameters;
configuring kafka connector and assigning a distinguishing key as a document number;
synchronizing the corresponding signing inquiry core form to topic according to the document number;
according to another preferred embodiment of the present invention, the signing query core form comprises: and starting a Kafka script in the Kafka cluster to execute synchronous operation on the signing and inquiring core form.
According to another preferred embodiment of the present invention, after the kafka connector is configured, the signing query core form in the PostgreSQL database is added to perform a monitoring operation on the signing query core form, so as to obtain the data of the changed signing query core form in real time.
According to another preferred embodiment of the present invention, 3 threads are started to capture the signed query core form data from the kafka cluster at specified intervals, and the signed query core form data and the change of the signed query core form data are determined, and different operations are respectively executed according to the changed data of different signed query core form data.
According to another preferred embodiment of the invention, the changed data of the private reimbursement bill table is obtained, whether the changed data of the private reimbursement bill table is a deletion instruction is judged, and if the changed data of the private reimbursement bill table is the deletion instruction, a data deletion object of an ElasticSearch search engine is established and used for deleting the data of the private reimbursement bill table; acquiring the changed data of the document table sold by the communique and judging whether the changed data is a deletion instruction, if so, establishing a data deletion object of an ElasticSearch search engine for deleting the document table data sold by the communique.
According to another preferred embodiment of the invention, the change data of the sign-in task table is obtained, if the change data is judged to be the update operation, a data update object of an ElasticSearch search engine is established; and obtaining the change data of the document approval task list, and if the change data is judged to be a deletion instruction and is an audit node, constructing a data object of updating audit passing time of the ElasticSearch, wherein the audit passing time is the current time.
According to another preferred embodiment of the present invention, the operation of synchronizing the encapsulated json format data into the ElasticSearch database further comprises the steps of:
constructing a Kafka cluster and an ElasticSearch database communication link;
constructing a signing object index, acquiring a designated field of a signing query core form, and segmenting the designated field;
storing the word segmentation result, and packaging the word segmentation result into json format data;
and calling a RestHighLevelClient interface to synchronize the encapsulated json format data object into the constructed index database.
In order to achieve at least one of the above objects, the present invention further provides a system for querying signed data, which uses the above method for querying signed data.
The invention further provides a computer readable storage medium, which stores and applies the signing data query application system.
Drawings
FIG. 1 is a flow chart illustrating a method for querying signed data according to the present invention.
FIG. 2 is a diagram of a system for querying signed data according to the present invention.
Detailed Description
The following description is presented to disclose the invention so as to enable any person skilled in the art to practice the invention. The preferred embodiments in the following description are given by way of example only, and other obvious variations will occur to those skilled in the art. The basic principles of the invention, as defined in the following description, may be applied to other embodiments, variations, modifications, equivalents, and other technical solutions without departing from the spirit and scope of the invention.
It is understood that the terms "a" and "an" should be interpreted as meaning that a number of one element or element is one in one embodiment, while a number of other elements is one in another embodiment, and the terms "a" and "an" should not be interpreted as limiting the number.
Referring to fig. 1-2, the present invention provides a method and a system for querying signed-in data, which convert the data of the signed-in query core form in the PostgreSQL database into data adapted to an ElasticSearch engine through a kafka cluster, thereby achieving the speed of signed-in query. Moreover, because the signing query operation is carried out through format conversion, open editing on the code level of the PostgreSQL database is not needed, the code coupling degree of the signing query can be reduced, and the development of signing application services is facilitated.
Specifically, the signing data query method comprises the following steps: firstly, kafka connectors need to be configured and registered, a communication link between a PostgreSQL database and a kafka cluster is established, 4 topics are further created in the kafka cluster, and the corresponding configuration parameters are as follows: design _ for _ task, pg.pro.reimburse _ data, pg.pro.corrp _ reimburse _ data, pg.prod.form _ ru _ task. The configuration parameters are used for acquiring and storing the signing query core form designated in the postgreSQL database, and the signing query core forms corresponding to the configuration parameters are respectively as follows: a sign _ for _ task table, a reimbursement receipt table (reimbursement _ data), a corporate _ reimbursement receipt table (corp _ reimbursement _ data), and a receipt approval task table (form _ ru _ task).
In the process of establishing a communication link with the kafka cluster, partition parameters are required to be configured, corresponding parameters are configured as transformations, partitions, key, list, and partition keys of the partition parameters are set as document numbers (formDataCodes) for identification and ordered storage of signed data. After a communication link is established between the configured and registered kafka connector and a PostgreSQL database, a signing query core form of the PostgreSQL database is written into a topic corresponding to the kafka cluster through Source, and the signing query core form data corresponding to the topic are sent to an ElasticSearch search engine database through Sink. In one preferred embodiment of the present invention, after configuring and registering the kafka connector, kafka script is used: and the connection-distributed.sh starts synchronous operation from the PostgreSQL database data to the kafka cluster, and the connection-distributed.sh script can start a plurality of processes through group.ip in the execution process and realize reading and forwarding of the data through the plurality of processes.
It should be noted that in one preferred embodiment of the present invention, during the process of acquiring the kafka cluster message, 3 threads need to be started and a controller. The maximum number of messages captured per batch may be set to 300.
Further, data change of a private reimbursement document table (reimburse _ data) under topic needs to be acquired, whether the data changed to the private reimbursement document table is a deletion operation is judged, if yes, a controller (controller) of the kafka cluster is used for constructing an ElasticSearch data deletion object, and the deletion object is defined as the private reimbursement document table. Acquiring data change of a document sales table (corp _ reimburse _ data) under topic, judging whether the data change of the document sales table is a deletion operation, and if so, constructing an ElasticSearch data deletion object through a controller (controller) of a kafka cluster, wherein the data deletion object is defined as the document sales table. Acquiring data change of a document approval task table (form _ ru _ task) under topic, if the data change is deletion operation and the node type is configured to be approved, constructing a data object of updating approval passing time of an elastic search through a controller (controller) of a kafka cluster, wherein the data object is defined as the document approval task table, and the approval passing time is the current time. Acquiring data change of a sign-in task table (sign _ for _ task) under topic, and if the changed data is judged to be updating operation, constructing a data updating object of ElasticSearch by a controller (controller) of a kafka cluster, wherein fields of the updating object are all fields in the sign _ for _ task topic.
Synchronizing the encapsulated data from the kafka cluster to the ElasticSearch database further comprises the steps of:
firstly, establishing a communication link with a kafka cluster and an elastic search database;
establishing an index of a signing object, and performing word segmentation on the specified fields of the 4 synchronous signing query core forms, so as to facilitate query operation on the 4 signing query core forms;
and synchronizing the encapsulated json format data object to the created index library by adopting RestHighLevelClient. It should be noted that the kafka cluster acquires 4 types of signing query core forms from the PostgreSQL database as map format data, and format conversion is required to be performed to convert the map format data into json format data.
The method for starting the signing query after completing the data synchronization comprises the following steps:
acquiring a query field of a user side, wherein the query field is actively input into an ElasticSearch search engine by the user;
translating the query field into supported QueryDSL expression parameters by the ElasticSearch search engine,
starting RestHighLevelClient according to the specified parameters of the QueryDSL expression to query the signing data in the ElasticSearch database, wherein the signing data with the maximum similarity can be found out according to a keyword matching mode;
and acquiring a query result, and transferring the query result to the user side.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section, and/or installed from a removable medium. The computer program, when executed by a Central Processing Unit (CPU), performs the above-described functions defined in the method of the present application. It should be noted that the computer readable medium mentioned above in the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wire segments, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless section, wire section, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be understood by those skilled in the art that the embodiments of the present invention described above and illustrated in the drawings are given by way of example only and not by way of limitation, the objects of the invention having been fully and effectively achieved, the functional and structural principles of the present invention having been shown and described in the embodiments, and that various changes or modifications may be made in the embodiments of the present invention without departing from such principles.
Claims (10)
1. A method for querying signed data, which is characterized by comprising the following steps:
acquiring a signing query core form in a PostgreSQL database, and establishing a communication link between the PostgreSQL database and a Kafka cluster;
synchronizing the check-in query core form to the Kafka cluster;
encapsulating the signing query core form into json data in the Kafka cluster;
and synchronizing the json data after encapsulation into an ElasticSearch database, and starting a signing query service.
2. The method of claim 1, wherein the synchronizing of the signed query core form comprises:
creating an acceptance table query core form topic in the Kafka cluster;
configuring corresponding signing inquiry core form parameters;
configuring kafka connector and assigning a distinguishing key as a document number;
and synchronizing the corresponding signing and inquiring core form to topic according to the document number.
3. The method of claim 1, wherein the signing query core form comprises: and starting a Kafka script in the Kafka cluster to execute synchronous operation on the signing and inquiring core form.
4. The method as claimed in claim 1, wherein after kafka connector is configured, adding a check-in query core form in a PostgreSQL database to perform a monitoring operation on the check-in query core form, so as to obtain the modified check-in query core form data in real time.
5. The method as claimed in claim 3, wherein 3 threads are started to capture the core form data of signed query from the kafka cluster at specified intervals, the change of the core form data of signed query is determined, and different operations are executed according to the changed data of different core form data of signed query.
6. The method according to claim 5, wherein the change data of the private reimbursement bill table is obtained, whether the change data of the private reimbursement bill table is a deletion instruction is judged, and if the change data of the private reimbursement bill table is the deletion instruction, a data deletion object of an ElasticSearch search engine is established and used for deleting the data of the private reimbursement bill table; acquiring the changed data of the document table sold by the communique and judging whether the changed data is a deletion instruction, if so, establishing a data deletion object of an ElasticSearch search engine for deleting the document table data sold by the communique.
7. The method according to claim 5, wherein the change data of the sign-off task table is obtained, and if the change data is judged to be an update operation, a data update object of an ElasticSearch search engine is established; and obtaining the change data of the document approval task list, and if the change data is judged to be a deletion instruction and is an audit node, constructing a data object of updating audit passing time of the ElasticSearch, wherein the audit passing time is the current time.
8. The method of claim 1, wherein the step of synchronizing the encapsulated json formatted data into the ElasticSearch database further comprises the steps of:
constructing a Kafka cluster and an ElasticSearch database communication link;
constructing a signing object index, acquiring a designated field of a signing query core form, and segmenting the designated field;
storing the word segmentation result, and packaging the word segmentation result into json format data;
and calling a RestHighLevelClient interface to synchronize the encapsulated json format data object into the constructed index database.
9. A check-in data query system, characterized in that the system employs a check-in data query method as claimed in any one of the preceding claims 1 to 8.
10. A computer-readable storage medium storing and using a system for signing data queries as claimed in claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110649208.6A CN113297274B (en) | 2021-06-10 | 2021-06-10 | Signing data query method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110649208.6A CN113297274B (en) | 2021-06-10 | 2021-06-10 | Signing data query method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113297274A true CN113297274A (en) | 2021-08-24 |
| CN113297274B CN113297274B (en) | 2023-09-01 |
Family
ID=77327888
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110649208.6A Active CN113297274B (en) | 2021-06-10 | 2021-06-10 | Signing data query method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113297274B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114564231A (en) * | 2022-02-28 | 2022-05-31 | 北京达佳互联信息技术有限公司 | Data query method, data query device, electronic equipment, medium and program product |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106326469A (en) * | 2016-08-31 | 2017-01-11 | 无锡雅座在线科技发展有限公司 | Synchronization method and device of data |
| US20170206249A1 (en) * | 2016-01-20 | 2017-07-20 | Systems And Methods For Implementing Urban Voices | Systems and methods for implementing urban voices |
| US20180107705A1 (en) * | 2016-10-19 | 2018-04-19 | Salesforce.Com, Inc. | Streamlined creation and updating of olap analytic databases |
| CN110275927A (en) * | 2019-06-26 | 2019-09-24 | 浪潮卓数大数据产业发展有限公司 | A kind of streaming real-time data synchronization system based on MySQL |
| US20200076578A1 (en) * | 2018-08-30 | 2020-03-05 | Netskope, Inc. | Methods And Systems For Securing And Retrieving Sensitive Data Using Indexable Databases |
| CN111597160A (en) * | 2020-04-21 | 2020-08-28 | 中国人民财产保险股份有限公司 | Distributed database system, distributed data processing method and device |
| CN112506992A (en) * | 2020-12-04 | 2021-03-16 | 中国人寿保险股份有限公司 | Fuzzy query method and device for Kafka data, electronic equipment and storage medium |
| CN112685446A (en) * | 2020-12-31 | 2021-04-20 | 上海梦鱼信息科技有限公司 | Complex SQL query method, device, processor and storage medium through Elasticissearch database |
| US10999370B1 (en) * | 2018-12-28 | 2021-05-04 | BridgeLabs, Inc. | Syncing and sharing data across systems |
-
2021
- 2021-06-10 CN CN202110649208.6A patent/CN113297274B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170206249A1 (en) * | 2016-01-20 | 2017-07-20 | Systems And Methods For Implementing Urban Voices | Systems and methods for implementing urban voices |
| CN106326469A (en) * | 2016-08-31 | 2017-01-11 | 无锡雅座在线科技发展有限公司 | Synchronization method and device of data |
| US20180107705A1 (en) * | 2016-10-19 | 2018-04-19 | Salesforce.Com, Inc. | Streamlined creation and updating of olap analytic databases |
| US20200076578A1 (en) * | 2018-08-30 | 2020-03-05 | Netskope, Inc. | Methods And Systems For Securing And Retrieving Sensitive Data Using Indexable Databases |
| US10999370B1 (en) * | 2018-12-28 | 2021-05-04 | BridgeLabs, Inc. | Syncing and sharing data across systems |
| CN110275927A (en) * | 2019-06-26 | 2019-09-24 | 浪潮卓数大数据产业发展有限公司 | A kind of streaming real-time data synchronization system based on MySQL |
| CN111597160A (en) * | 2020-04-21 | 2020-08-28 | 中国人民财产保险股份有限公司 | Distributed database system, distributed data processing method and device |
| CN112506992A (en) * | 2020-12-04 | 2021-03-16 | 中国人寿保险股份有限公司 | Fuzzy query method and device for Kafka data, electronic equipment and storage medium |
| CN112685446A (en) * | 2020-12-31 | 2021-04-20 | 上海梦鱼信息科技有限公司 | Complex SQL query method, device, processor and storage medium through Elasticissearch database |
Non-Patent Citations (2)
| Title |
|---|
| 为何不可1995: "干货：使用Kafka connect 同步数据至Elasticsearch", 《HTTPS://MY.OSCHINA.NET/U/3734816/BLOG/4298226》, 1 June 2020 (2020-06-01), pages 1 - 2 * |
| 前嗅: "干货：使用Kafka connect 同步数据至Elasticsearch", pages 1 - 2, Retrieved from the Internet <URL:《http://www.forenose.com/column/content/427083577.html》> * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114564231A (en) * | 2022-02-28 | 2022-05-31 | 北京达佳互联信息技术有限公司 | Data query method, data query device, electronic equipment, medium and program product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113297274B (en) | 2023-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111581291A (en) | Data processing method and device, electronic equipment and readable medium | |
| CN110321252B (en) | Skill service resource scheduling method and device | |
| CN111038906A (en) | Order sorting method and device | |
| CN110851511A (en) | Data synchronization method and device | |
| CN115033646B (en) | Method for constructing real-time warehouse system based on Flink and Doris | |
| CN105786941B (en) | Information mining method and device | |
| CN113297274B (en) | Signing data query method and system | |
| CN113342686A (en) | Test data generation method and device | |
| CN110764769B (en) | Method and device for processing user request | |
| CN111814020A (en) | Data acquisition method and device | |
| CN111241137A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN112000669B (en) | Environment monitoring data processing method and device, storage medium and terminal | |
| CN117009430A (en) | Data management method, device, storage medium and electronic equipment | |
| CN113297240A (en) | PostgreSQL database synchronization method and system | |
| CN115794876A (en) | Fragment processing method, device, equipment and storage medium for service data packet | |
| CN113342865A (en) | Reimbursement bill examination and approval query method and system | |
| CN110109919B (en) | Method and device for determining logic information | |
| CN112306695A (en) | Data processing method and device, electronic equipment and computer storage medium | |
| CN113515285A (en) | Method and device for generating real-time calculation logic data | |
| CN112307061A (en) | Method and device for querying data | |
| CN112311833B (en) | Data updating method and device | |
| CN114997416A (en) | Training method and training single machine of deep learning model | |
| CN108536362B (en) | Method and device for identifying operation and server | |
| CN115328916A (en) | Method, device and equipment for constructing secondary index table and storage medium | |
| CN116662350A (en) | Method, device, equipment and storage medium for inquiring return list |
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 |