CN111291038A - Data query method and device - Google Patents
Data query method and device Download PDFInfo
- Publication number
- CN111291038A CN111291038A CN201811485958.9A CN201811485958A CN111291038A CN 111291038 A CN111291038 A CN 111291038A CN 201811485958 A CN201811485958 A CN 201811485958A CN 111291038 A CN111291038 A CN 111291038A
- Authority
- CN
- China
- Prior art keywords
- data
- downstream
- data processing
- identification
- intermediate layer
- 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
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000012545 processing Methods 0.000 claims abstract description 106
- 230000008569 process Effects 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- 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
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data query method and a data query device, and relates to the technical field of computers. One embodiment of the method comprises: adding downstream data identifiers to intermediate layer data in multi-stage data processing, wherein each stage of data processing uses at least one dimension to generate a layer of data, the intermediate layer data is data generated by data processing of all stages except the last stage of data processing, and the identifiers are determined according to the dimensions used by the data processing of all stages when the downstream data is generated; and querying data used for generating the downstream data according to the identification. According to the implementation method, data write-back is not needed, the data processing and querying performance can be improved, the development cost is saved, the timeliness is enhanced, and the data querying overhead is reduced.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a data query method and device.
Background
In a large amount of data query scenarios, data write-back needs to be performed first, so that corresponding data can be queried according to the written-back data in subsequent queries. For example, in a settlement business scenario, when a business system interacts with a settlement system, the logic of data processing includes: the service system generates service data, charges the service data to generate charging details, generates settlement details by summarizing the charging details, generates a settlement sheet by summarizing the settlement details, pushes the settlement sheet to the settlement system, generates a settlement sheet number after the settlement system receives the settlement sheet, and then sends the settlement sheet number back to the service system, and the service system backfills the received settlement sheet number to the charging details, the settlement details and the settlement sheet. And in the subsequent inquiry, inquiring the corresponding data such as the charging detail, the settlement detail and the like according to the settlement list number.
Currently, as the data amount increases, the write-back of the statement number becomes a great performance overhead, even in an extreme case, the write-back of the data affects the financial reconciliation period, and when the charging details need to be inquired from the statement, the data inquiry overhead must be increased through the settlement details inquiry.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
the existing scheme greatly influences the performance of data processing and query, has high development cost and low timeliness, and increases the overhead of data query.
Disclosure of Invention
In view of this, embodiments of the present invention provide a data query method and apparatus, which do not need to write back data, can improve data processing and query performance, save development cost, enhance timeliness, and reduce data query overhead.
To achieve the above object, according to an aspect of an embodiment of the present invention, a data query method is provided.
A method of data query, comprising: adding downstream data identifiers to intermediate layer data in multi-stage data processing, wherein each stage of data processing uses at least one dimension to generate a layer of data, the intermediate layer data is data generated by data processing of all stages except the last stage of data processing, and the identifiers are determined according to the dimensions used by the data processing of all stages when the downstream data is generated; and querying data used for generating the downstream data according to the identification.
Optionally, the downstream data of each intermediate layer data includes a final result of the multi-stage data processing, where the final result is data generated by the last stage data processing, and the step of querying the data used for generating the downstream data according to the identifier includes: and inquiring one or more layers of specified data used for generating the final result according to the identifier of the final result.
Optionally, the downstream data of each intermediate layer data includes downstream intermediate layer data of the layer, and the step of querying the data for generating the downstream data according to the identifier includes: querying the specified one or more layers of data used to generate the downstream intermediate layer data based on an identification of the downstream intermediate layer data.
Optionally, the step of adding an identifier of downstream data to intermediate layer data in the multi-stage data processing includes: splicing fields related to dimensionality used by data processing of each level when the downstream data are generated to determine the identification of the downstream data; adding the determined identity of the downstream data to the corresponding middle tier data.
According to another aspect of the embodiments of the present invention, a data query apparatus is provided.
A data query apparatus, comprising: the identification adding module is used for adding identification of downstream data to middle layer data in multi-stage data processing, each stage of data processing uses at least one dimension to generate a layer of data, the middle layer data is data generated by data processing of each stage except the last stage of data processing, and the identification is determined according to the dimension used by the data processing of each stage when the downstream data is generated; and the data query module is used for querying the data used for generating the downstream data according to the identification.
Optionally, the downstream data of each intermediate layer data includes a final result of the multi-stage data processing, where the final result is data generated by the last stage data processing, and the data query module is further configured to: and inquiring one or more layers of specified data used for generating the final result according to the identifier of the final result.
Optionally, the downstream data of each intermediate layer data includes intermediate layer data downstream of the layer, and the data query module is further configured to: querying the specified one or more layers of data used to generate the downstream intermediate layer data based on an identification of the downstream intermediate layer data.
Optionally, the identifier adding module is further configured to: splicing fields related to dimensionality used by data processing of each level when the downstream data are generated to determine the identification of the downstream data; adding the determined identity of the downstream data to the corresponding middle tier data.
According to yet another aspect of an embodiment of the present invention, an electronic device is provided.
An electronic device, comprising: one or more processors; a memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the data query method provided by the present invention.
According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.
A computer-readable medium, on which a computer program is stored, which, when executed by a processor, implements the data query method provided by the present invention.
One embodiment of the above invention has the following advantages or benefits: adding downstream data identifiers to intermediate layer data in the multi-stage data processing, wherein each stage of data processing uses at least one dimension to generate a layer of data, the intermediate layer data is data generated by data processing of all stages except the last stage of data processing, and the identifiers are determined according to the dimensions used by the data processing of all stages when the downstream data is generated; data used to generate downstream data is queried based on the identification. The invention does not need to write back data, can improve the performance of data processing and query, saves the development cost, enhances the timeliness and reduces the expenditure of data query.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a diagram illustrating the main steps of a data query method according to an embodiment of the present invention;
FIG. 2 is a flow diagram of a data query method according to one embodiment of the invention;
FIG. 3 is a schematic diagram of a data query for a settlement service scenario, according to one embodiment of the invention;
FIG. 4 is a schematic diagram of the main modules of a data query device according to an embodiment of the present invention;
FIG. 5 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
FIG. 6 is a schematic block diagram of a computer system suitable for use with a server implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of main steps of a data query method according to an embodiment of the present invention.
As shown in fig. 1, the data query method according to the embodiment of the present invention mainly includes the following steps S101 to S102.
Step S101: and adding the identification of the downstream data to the intermediate layer data in the multi-stage data processing.
Each link in the business process generates data through data processing, the business process comprises multi-level data processing, each level of data processing uses at least one dimension to generate a layer of data, and the middle layer of data is data generated by data processing of each level except the last level of data processing. That is, the data processing result of each link in the business process is called first-layer data, and the data processing results of other links except the last link are called middle-layer data.
The identification of the added downstream data is determined according to the dimension used by each level of data processing when the downstream data is generated.
It should be noted that, when the downstream data is generated, the identifier is also added to the downstream data.
Specifically, step S101 may include: splicing fields related to dimensionality used by data processing of each level when the downstream data is generated to determine the identification of the downstream data; adding the determined identity of the downstream data to the corresponding middle tier data.
The downstream data of a certain intermediate layer data can be data generated by a subsequent data processing link of the layer data. The final result of the multi-stage data processing, that is, the data generated by the last stage of data processing, may be included. Intermediate layer data downstream of this layer may also be included.
Step S102: and inquiring data for generating certain downstream data according to the identifier added by each layer of data.
In particular, a specified layer or layers of data used to generate the final result of the added multi-level data processing may be queried based on the identification of the final result.
Or inquiring the specified layer or layers of data for generating the downstream intermediate layer data according to the identification of the added downstream intermediate layer data.
The data query method according to the embodiment of the present invention is described below by taking a settlement service scenario as an example. It should be noted that the present invention is not limited to data query in settlement service scenarios, but can also be used for data query in other scenarios.
In a settlement service scene, a service flow comprises multilevel data processing such as generating charging details for service data charging, generating settlement details for charging details summarizing, generating a settlement list for settlement details summarizing, and the like. The charging detail and the settlement detail are intermediate layer data of the multi-stage data processing, wherein the settlement detail is downstream intermediate layer data of the charging detail, and the settlement list is a final result of the multi-stage data processing, namely data generated by the last stage data processing, and is a basis for settlement between the two main bodies.
The services after generating the statement of account include payment and invoicing, and when a certain statement of account completes the post-services such as payment and invoicing, the state of the statement of account is changed (for example, the original unpaid statement is changed into a paid and invoiced statement).
When the state change of the statement is completed, the statement in the latest state and the corresponding billing detail and settlement detail need to be pushed to the downstream system, which may be all systems that need to obtain the relevant data (statement, billing detail, settlement detail) of the statement, such as an EBS (electronic commerce suite) system for generating a statement, a system for auditing payment services, and so on. Before the data related to the bill of settlement is sent to the downstream system, the data such as the charging particulars and the settlement particulars corresponding to the bill of settlement needs to be inquired, namely the data such as the charging particulars and the settlement particulars used when the bill of settlement is generated in an inquiring and summarizing manner.
If the downstream system only needs the charging detail data under a certain settlement detail, the downstream system can also only inquire the charging detail corresponding to the certain settlement detail, namely only inquire the data of the charging detail used when the settlement detail is generated in a summary mode.
Fig. 2 is a flow chart diagram of a data query method according to an embodiment of the invention. Including step S201 to step S204.
Step S201: and when the charging detail is generated according to the service data charging, adding a settlement detail identifier and a settlement order identifier to the charging detail.
The settlement detail identifier, i.e., the settlement detail uuid (universal unique identification code), is determined from dimensions (which may be referred to as summary dimensions) used when the settlement details are generated in summary. Specifically, the fields related to the summary dimension when the settlement detail is generated may be concatenated to obtain the settlement detail identifier. For example, a settlement detail is formed by grouping and summarizing a and B fields in the charging detail, and then the settlement detail identifier is a Key (Key) formed by spelling the values of a and B, and the settlement detail identifier can be represented by "detailKey".
And the settlement list identification, namely the settlement list uuid, is determined according to the dimension used for summarizing the data at each level when the settlement list is generated. Specifically, for example, based on the above-mentioned statement of settlement, the statement of settlement is generated by summarizing according to the dimension X, and then the statement of settlement identifier is the value concatenation of a and B, and then the value concatenation of a and B is performed, and the statement of settlement identifier can be identified by "mainKey".
When the settlement statement and the settlement ticket are generated, the settlement statement identifier and the settlement ticket identifier are also added to the generated settlement statement and the generated settlement ticket, respectively (see step S202 and step S203 in detail).
In this embodiment, both the settlement statement and the settlement statement may be called downstream data of the charging statement, the settlement statement is the downstream data of the settlement statement, and the charging statement and the settlement statement belong to intermediate layer data of multi-stage data processing, where the settlement statement is also the downstream intermediate layer data of the charging statement. The settlement list is the final result of the multi-stage data processing, namely the data generated by the last stage of data processing.
Step S202: and when the settlement details are generated according to the summary of the charging details, adding a settlement detail identifier and a settlement order identifier to the settlement details.
Step S203: and when the settlement statement is generated according to the settlement detail collection, adding a settlement statement identifier to the settlement statement.
Step S204: inquiring corresponding settlement details and/or charging details under a certain settlement list according to the settlement list identification; or inquiring the corresponding charging detail under a certain settlement detail according to the settlement detail identification.
According to the requirement of a downstream system, the bill with the bill identification, all the bills with the bill identification and the accounting details, or only one of the bill with the bill identification and the accounting details can be inquired according to the mailkey of a certain bill identification. Or inquiring the settlement detail with the settlement detail identifier and all the charging details with the settlement detail identifier according to a certain settlement detail identifier detailKey.
Referring to the above flow, a schematic diagram of data query of a settlement service scenario is shown in fig. 3. In fig. 3, the basic service data is the above-mentioned service data, and the charging result is the charging details, and fig. 3 shows an embodiment of querying all the charging details under a certain bill based on the bill identifier mainKey and querying all the charging details under a certain bill based on the bill identifier detailKey, where the charging details are generated by summarizing (merging) the charging results according to a dimension such as A, B, C, and the bill is generated by summarizing (merging) the charging details according to a dimension such as A, B, C, D.
In another embodiment, if the service scenario only needs to query the final result of the multi-level data processing for the corresponding layers of data, the identifier for adding the downstream data to the intermediate layer data in the multi-level data processing may only include the identifier for the final result of the multi-level data processing.
In another embodiment, if the service scenario only needs to query the corresponding data of each layer for the intermediate layer data, the identifier of the downstream data added to the intermediate layer data in the multi-level data processing may only include the identifier of the data of each intermediate layer downstream of the layer.
The embodiment of the invention can generate the settlement detail identification and the settlement list identification when generating the charging detail, thereby removing the logic of writing back the settlement list number in the prior art, reducing the system performance overhead, ensuring the financial account period, saving the development cost, improving the time efficiency, and optimizing the data query.
Fig. 4 is a schematic diagram of main blocks of a data query device according to an embodiment of the present invention.
The data query apparatus 400 of the embodiment of the present invention mainly includes: an identification adding module 401 and a data query module 402.
The identifier adding module 401 is configured to add an identifier of downstream data to middle layer data in multiple levels of data processing, where each level of data processing uses at least one dimension to generate a layer of data, the middle layer data is data generated by data processing at each level except for the last level of data processing, and the identifier is determined according to the dimension used by data processing at each level when the downstream data is generated.
Each link in the business process generates data through data processing, the whole business process comprises multi-level data processing, each level of data processing uses at least one dimension to generate a layer of data, and the middle layer of data is data generated by data processing of each level except the last level of data processing. That is, the data processing result of each link in the business process is called first-layer data, and the data processing results of other links except the last link are called middle-layer data.
The downstream data of a certain intermediate layer data can be data generated by a subsequent data processing link of the layer data. The final result of the multi-stage data processing, that is, the data generated by the last stage of data processing, may be included. Intermediate layer data downstream of this layer may also be included.
The identifier adding module 401 may specifically be configured to: splicing fields related to dimensionality used by data processing of each level when the downstream data is generated to determine the identification of the downstream data; adding the determined identity of the downstream data to the corresponding middle tier data.
A data query module 402, configured to query the data used to generate the downstream data according to the added identifier.
The data query module 402 may be further configured to: based on the identification of a downstream intermediate layer of data, a query is made for one or more layers of data specified to generate the downstream intermediate layer of data.
In addition, the detailed implementation of the data query device in the embodiment of the present invention has been described in detail in the above data query method, so that repeated descriptions herein are not repeated.
Fig. 5 illustrates an exemplary system architecture 500 of a data query method or data query apparatus to which embodiments of the invention may be applied.
As shown in fig. 5, the system architecture 500 may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 serves to provide a medium for communication links between the terminal devices 501, 502, 503 and the server 505. Network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 501, 502, 503 to interact with a server 505 over a network 504 to receive or send messages or the like. The terminal devices 501, 502, 503 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 501, 502, 503 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 505 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 501, 502, 503. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the data query method provided by the embodiment of the present invention is generally executed by the server 505, and accordingly, the data query apparatus is generally disposed in the server 505.
It should be understood that the number of terminal devices, networks, and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing a server according to embodiments of the present application. The server shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.
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 through the communication section 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present application are executed when the computer program is executed by the Central Processing Unit (CPU) 601.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A 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 wires, 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, wire, 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 application. 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 or flowchart illustration, and combinations of blocks in the block diagrams 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.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises an identification adding module and a data query module. The names of these modules do not in some cases constitute a limitation on the module itself, and for example, the identification addition module may also be described as a "module for adding identification of downstream data to middle layer data in a multi-level data process".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: adding downstream data identifiers to intermediate layer data in multi-stage data processing, wherein each stage of data processing uses at least one dimension to generate a layer of data, the intermediate layer data is data generated by data processing of all stages except the last stage of data processing, and the identifiers are determined according to the dimensions used by the data processing of all stages when the downstream data is generated; and querying data used for generating the downstream data according to the identification.
According to the technical scheme of the embodiment of the invention, downstream data identification is added to middle layer data in multi-stage data processing, each stage of data processing uses at least one dimension to generate a layer of data, the middle layer data is data generated by data processing of each stage except the last stage of data processing, and the identification is determined according to the dimension used by the data processing of each stage when the downstream data is generated; data used to generate downstream data is queried based on the identification. Data write-back is not needed, the data processing and query performance can be improved, the development cost is saved, the timeliness is enhanced, and the data query overhead is reduced.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for querying data, comprising:
adding downstream data identifiers to intermediate layer data in multi-stage data processing, wherein each stage of data processing uses at least one dimension to generate a layer of data, the intermediate layer data is data generated by data processing of all stages except the last stage of data processing, and the identifiers are determined according to the dimensions used by the data processing of all stages when the downstream data is generated;
and querying data used for generating the downstream data according to the identification.
2. The method of claim 1, wherein the downstream data of each intermediate layer data includes a final result of the multi-stage data processing, the final result being data generated by the last stage data processing,
querying, based on the identification, data used to generate the downstream data, comprising:
and inquiring one or more layers of specified data used for generating the final result according to the identifier of the final result.
3. The method of claim 1, wherein the data downstream of each intermediate layer data comprises intermediate layer data downstream of the layer,
querying, based on the identification, data used to generate the downstream data, comprising:
querying the specified one or more layers of data used to generate the downstream intermediate layer data based on an identification of the downstream intermediate layer data.
4. The method of claim 1, wherein the step of adding an identification of downstream data to intermediate tier data in a multi-tier data process comprises:
splicing fields related to dimensionality used by data processing of each level when the downstream data are generated to determine the identification of the downstream data;
adding the determined identity of the downstream data to the corresponding middle tier data.
5. A data query apparatus, comprising:
the identification adding module is used for adding identification of downstream data to middle layer data in multi-stage data processing, each stage of data processing uses at least one dimension to generate a layer of data, the middle layer data is data generated by data processing of each stage except the last stage of data processing, and the identification is determined according to the dimension used by the data processing of each stage when the downstream data is generated;
and the data query module is used for querying the data used for generating the downstream data according to the identification.
6. The apparatus of claim 5, wherein the downstream data of each intermediate layer data includes a final result of the multi-stage data processing, the final result being data generated by the last stage data processing,
the data query module is further configured to:
and inquiring one or more layers of specified data used for generating the final result according to the identifier of the final result.
7. The apparatus of claim 5, wherein the data downstream of each intermediate layer data comprises intermediate layer data downstream of the layer,
the data query module is further configured to:
querying the specified one or more layers of data used to generate the downstream intermediate layer data based on an identification of the downstream intermediate layer data.
8. The apparatus of claim 5, wherein the identity addition module is further configured to:
splicing fields related to dimensionality used by data processing of each level when the downstream data are generated to determine the identification of the downstream data;
adding the determined identity of the downstream data to the corresponding middle tier data.
9. An electronic device, comprising:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-4.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811485958.9A CN111291038B (en) | 2018-12-06 | 2018-12-06 | Data query method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811485958.9A CN111291038B (en) | 2018-12-06 | 2018-12-06 | Data query method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111291038A true CN111291038A (en) | 2020-06-16 |
| CN111291038B CN111291038B (en) | 2024-01-12 |
Family
ID=71016795
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811485958.9A Active CN111291038B (en) | 2018-12-06 | 2018-12-06 | Data query method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111291038B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080027788A1 (en) * | 2006-07-28 | 2008-01-31 | Lawrence John A | Object Oriented System and Method for Optimizing the Execution of Marketing Segmentations |
| CN101894149A (en) * | 2010-06-23 | 2010-11-24 | 畅捷通软件有限公司 | Method and device for tracking and inquiring document |
| CN103116832A (en) * | 2011-11-16 | 2013-05-22 | 航天信息软件技术有限公司 | Method and device for grouping collecting and generating business documents |
| CN107861825A (en) * | 2017-10-16 | 2018-03-30 | 北京京东尚科信息技术有限公司 | Request processing/conditional code querying method and device, lower/upper trip node, medium |
-
2018
- 2018-12-06 CN CN201811485958.9A patent/CN111291038B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080027788A1 (en) * | 2006-07-28 | 2008-01-31 | Lawrence John A | Object Oriented System and Method for Optimizing the Execution of Marketing Segmentations |
| CN101894149A (en) * | 2010-06-23 | 2010-11-24 | 畅捷通软件有限公司 | Method and device for tracking and inquiring document |
| CN103116832A (en) * | 2011-11-16 | 2013-05-22 | 航天信息软件技术有限公司 | Method and device for grouping collecting and generating business documents |
| CN107861825A (en) * | 2017-10-16 | 2018-03-30 | 北京京东尚科信息技术有限公司 | Request processing/conditional code querying method and device, lower/upper trip node, medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111291038B (en) | 2024-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110706093A (en) | Accounting processing method and device | |
| CN111127181B (en) | Voucher accounting method and device | |
| CN111460129A (en) | Method and device for generating identification, electronic equipment and storage medium | |
| CN110909022A (en) | Data query method and device | |
| CN111080424A (en) | Accounting management method and device | |
| CN112884405A (en) | Inquiry system and scheduling method thereof | |
| CN112132674A (en) | Transaction processing method and device | |
| CN111857888A (en) | Transaction processing method and device | |
| CN111881329A (en) | Account balance management method and system | |
| CN110705981B (en) | Real-time settlement method and device | |
| CN110648216A (en) | Wind control method and device | |
| CN110865797A (en) | Method and device for processing dynamic attributes of services | |
| CN113742389A (en) | Service processing method and device | |
| CN110866001A (en) | Method and device for determining order to be processed | |
| CN112884181A (en) | Quota information processing method and device | |
| CN113761565A (en) | Data desensitization method and apparatus | |
| CN113641706A (en) | Data query method and device | |
| CN112948138A (en) | Method and device for processing message | |
| CN112990991A (en) | Method and device for merging invoices | |
| CN113641633B (en) | File processing method, apparatus, electronic device, medium, and computer program | |
| CN111291038B (en) | Data query method and device | |
| CN113704222A (en) | Method and device for processing service request | |
| CN112131287A (en) | Method and device for reading data | |
| CN110888939A (en) | Data management method and device | |
| CN113780921B (en) | Price inquiry processing method and device |
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 |