WO2021073242A1 - Procédés, appareil et dispositif de création d'index et d'interrogation de données - Google Patents
Procédés, appareil et dispositif de création d'index et d'interrogation de données Download PDFInfo
- Publication number
- WO2021073242A1 WO2021073242A1 PCT/CN2020/109289 CN2020109289W WO2021073242A1 WO 2021073242 A1 WO2021073242 A1 WO 2021073242A1 CN 2020109289 W CN2020109289 W CN 2020109289W WO 2021073242 A1 WO2021073242 A1 WO 2021073242A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- block
- data block
- business
- data record
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000000903 blocking effect Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 10
- 230000008520 organization Effects 0.000 description 10
- 238000012795 verification Methods 0.000 description 8
- 238000003032 molecular docking Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 239000006227 byproduct Substances 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2272—Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2255—Hash tables
-
- 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/2457—Query processing with adaptation to user needs
- G06F16/24578—Query processing with adaptation to user needs using ranking
Definitions
- the embodiments of this specification relate to the field of information technology, and in particular to methods, devices and equipment for index creation and data query.
- the ledger records the relevant data records that the relevant users need to save.
- data records that need to be stored by users docked by a centralized database server often have different business attributes.
- the source of the data record the user, the project it belongs to, and so on.
- the storage of data records related to the same business attribute is often disordered, and the results obtained by user queries are often disordered.
- the purpose of the embodiments of the present application is to provide an index creation and query solution for implementing an orderly query on a blockchain ledger.
- the embodiment of this specification provides an index creation method, which is applied to a centralized database server that stores data through a block chain ledger, including: obtaining business attributes and numbers contained in data records, wherein the The number is determined by the client; the location information of the data record in the ledger is determined, the location information includes the block height of the data block where the data record is located, and the offset in the data block where the data record is located; A merge field containing a business attribute and a serial number; the corresponding relationship between the merge field and location information is established, and an index with the merge field as the primary key is written.
- the embodiment of this specification provides a data query method based on the aforementioned index, including: receiving a query instruction containing business attributes; matching from an index table according to the business attributes, and determining that the index table contains The location information corresponding to each primary key of the business attribute; obtain corresponding data records from the ledger according to the location information, and return the obtained corresponding data records to the query instruction sender.
- the embodiment of this specification also provides a query device based on the aforementioned index, including: an instruction receiving module, which receives a query instruction including business attributes; and a matching module, which performs matching from the index table according to the business attributes , Determine the location information corresponding to each primary key containing the business attribute in the index table; the data acquisition module acquires the corresponding data record from the ledger according to the location information, and returns the acquired corresponding data Record to the sender of the query instruction.
- the business attributes and numbers of the data records are determined, and the merge field containing the business attributes and numbers is generated, and the storage location in the ledger is established to establish the merge field Correspondence with location information, so that the number information specified by the user is included in the index, and then when the user needs to query, the database server can get the orderly query result according to the number in the merge field and return it to the user , To achieve orderly query in the blockchain ledger.
- any one of the embodiments of the present specification does not need to achieve all the above-mentioned effects.
- Figure 1 is a schematic diagram of the system architecture involved in an embodiment of the specification
- Fig. 2 is a schematic diagram of a process for generating a block chain ledger provided by an embodiment of the specification
- FIG. 3 is a schematic diagram of a block header of a data block provided by an embodiment of this specification.
- FIG. 5 is a schematic flowchart of a data query method based on the aforementioned index provided by an embodiment of this specification;
- FIG. 6 is an index creation device provided by an embodiment of this specification.
- FIG. 7 is a schematic structural diagram of a query device provided by an embodiment of this specification.
- Fig. 8 is a schematic structural diagram of a device for configuring the method of the embodiment of this specification.
- FIG. 1 is a schematic diagram of a system architecture involved in an embodiment of the specification.
- an enterprise organization can face multiple users, and each user can query the database service provider through its corresponding enterprise organization.
- the organization connected to the database server is a financial product company, and the data records can be individual users’ financial management records in the financial product company; or, the connected organization can be a government department, where the data records are what the government department has for the department. Expense details of the managed public project; or, the database server is connected to a hospital, and the data record is the patient’s medical record; or the database server is connected to a third-party payment agency, and the data record can be an individual user Payment records through the agency, and so on.
- FIG. 2 is a schematic diagram of the process of generating a block chain ledger provided by the embodiment of this specification, including S201 to S203 .
- S201 Receive a data record to be stored, and determine a hash value of each data record, where the data record includes a business attribute and a serial number.
- the data records to be stored here can be various consumption records of individual users of the client, or can be business results, intermediate states, and operation records generated when the application server executes business logic based on user instructions.
- Specific business scenarios can include consumption records, audit logs, supply chains, government supervision records, medical records, and so on.
- the number here is a numeric string, which is determined by the client. Specifically, it can be determined in the following manner.
- the first type is specified by the user through the client.
- a writable option of the number is provided in the client interface.
- the user fills in the number by himself, and the client generates data containing business attributes and numbers according to the number entered by the user recording. For example, according to the time sequence of the user's medical records, fill in the serial numbers one by one to obtain multiple medical records containing serial numbers. In this way, the serial numbers directly reflect the order of the data records uploaded by the user.
- the second type is determined by the client based on the preset business logic. For example, a counter for numbering is preset in the client. Each time the user uploads a data record through the client, the number value is automatically +1, and the The number value is written to the data record. In this way, the number value reflects the upload order of the user on the client, and indirectly expresses the order of the data records uploaded by the user.
- S203 When a preset block forming condition is reached, determine each data record to be written in the data block, and generate an Nth data block including the hash value of the data block and the data record.
- the preset blocking conditions include: the number of data records to be stored reaches the number threshold, for example, every time one thousand data records are received, a new data block is generated and one thousand data records are written into the block; or , The time interval from the last block formation time reaches the time threshold, for example, every 5 minutes, a new data block is generated, and the data records received within these 5 minutes are written into the block.
- N refers to the number of the data block.
- the data block is in the form of a block chain, which is arranged sequentially based on the order of the block time, and has strong timing characteristics.
- the block height of the data block increases monotonically based on the sequence of the block time.
- the block height can be a number.
- the block height of the Nth data block is N; the block height can also be generated in other ways.
- the data block at this time is the initial data block.
- the current data block (the first data block) can be generated based on the hash value of the previous data block (that is, the N-1th data block). For example, a feasible way is to determine the hash value of each data record to be written in the Nth block, and generate a Merck according to the order in the block.
- the root hash value of the Merkel tree and the hash value of the previous data block are spliced together, and the hash algorithm is used again to generate the hash value of the current block.
- the data block generated in the above manner may include two parts: a block header and a block body.
- the block body can be used to store the plaintext of the spliced data, or the hash value of the spliced data, etc.;
- the block header can be used to store metadata about the data block, for example, the version number of the ledger, the hash of the previous data block Value, the root hash value of the Merkel tree composed of the spliced data in the own data block, the hash value of the own data block, the state array used to record the operated state of the spliced data, and so on.
- FIG. 3 is a schematic diagram of a block header of a data block provided by an embodiment of this specification.
- the hash value of the corresponding data record and the hash value of the data block can be obtained and saved, and integrity verification can be initiated based on the hash value.
- the specific verification method is to recalculate the hash value of the data record itself and the hash value of the data block in the database, and compare with the locally stored hash value.
- each data block is determined by a hash value
- the hash value of the data block is determined by the content and order of the data records in the data block and the hash value of the previous data block.
- the user can initiate verification based on the hash value of the data block at any time. Any modification of the content of the data block (including the modification of the data record content or sequence in the data block) will result in the hash value of the data block calculated during verification.
- the hash value of the data block is inconsistent when it is generated, which causes the verification to fail, thus realizing the immutability under centralization.
- a segment of data block is designated for continuous integrity verification, or continuous integrity verification is performed from the initial data block.
- the verification method is to obtain the hash value of the previous data block, and use the same algorithm as when generating the hash value of the data block, and recalculate its own data according to its own data record and the hash value of the previous data block. The hash value of the block.
- FIG. 4 is a schematic flow chart of an index creation method provided by an embodiment of this specification, and the flow specifically includes the following steps S401 to S407.
- S401 Acquire business attributes and serial numbers included in the data record, where the serial numbers are determined by the client.
- the location and acquisition method of the business attribute in the data record may be negotiated in advance by the database server and the docking organization.
- the business attributes can be obtained from the specified offset in the data record, or the start and end positions can be identified by specific characters; or, the docking organization provides
- the header containing the business attribute and number can be directly spliced at the beginning of each data record when the docking agency uploads it, and the database server can directly obtain the data record of each data record from the header.
- Business attributes and numbers are examples of the business attribute and numbers.
- S403 Determine location information of the data record in the ledger, where the location information includes the block height of the data block where the data record is located, and the offset in the data block where the data record is located.
- a block-chain ledger is composed of multiple data blocks, and at the same time, a data block usually contains multiple data records. Therefore, in the embodiment of this specification, the location information specifically refers to which data block in the ledger is located when a data record is saved, and where it is in the data block.
- the hash value of the data block is a hash value obtained by hash calculation based on the previous block's hash value and its own data record, which can be used to uniquely and unambiguously identify a data block.
- the block height of the first data block is 0, and the block height is increased by 1 for each additional data block; or, the block time of the data block can be converted into a large monotonic increase Integer data (usually 12 to 15 bits) sequence, as the block height of the data block. Therefore, a data block usually has a clear block height.
- the order of the data records has also been fixed, so the serial number of a data record in the data block is also clear.
- the sequence number in the data block can also be used to clarify the position information of the data record in the data block. That is, the sequence number in the data block can also be used to indicate the offset.
- the address offset of each data record in the data block can also be used to identify the data records in the data block respectively.
- the address offset of each data record is not the same.
- the specific format of the data block can be customized (for example, the metadata information and remark information contained in the block header of the data block, and the block height of the data block is adopted Format, etc.), in different formats, the content of the location information will also be different, which does not constitute a limitation to this solution.
- S405 Generate a merge field including the business attribute and the serial number.
- the business attribute and the serial number can be directly spliced, which can be in the form of business attribute + serial number, or can be in the form of serial number + business attribute.
- S407 Establish a corresponding relationship between the merge field and location information, and write an index with the merge field as the primary key.
- Table 1 is an exemplary index table provided in the embodiment of this specification.
- Key is a merged field containing business attributes and serial numbers
- an array of Value part is a piece of position information.
- the first part of the array is the block height
- the latter part is the serial number of the data recorded in the data block, passing the block height and serial number That is, a data record can be uniquely determined.
- a key uniquely corresponds to one location information.
- "Bingli” is the business attribute
- "001" is the number given by the client.
- Bingli001 (2,08) Bingli003 (2,10) Bingli002 (3,99) ... ...
- an acquisition method can be created synchronously, that is, when the data record is received, the business attribute and number are directly parsed, and the merged field is obtained.
- an index is created synchronously. Another way is that after the data block is written into the ledger, there is no need to create an index immediately, but when the database has free resources, the business attributes are obtained for each data record in the newly written data block of the ledger. And number, generate merged fields, realize asynchronous creation of index, in the way of asynchronous creation, it is conducive to the database server to save resources.
- the serial number may be spliced after the business attribute to generate a merged field containing the business attribute and the serial number.
- the merge fields may also be sorted according to the numbers contained in the merge fields, and the merge fields may be sequentially written into the index with the merge field as the primary key.
- sorting is performed according to the numbers of "Bingli001”, “Bingli003” and “Bingli002”, so as to realize the primary keys "Bingli001”, “Bingli002” and “Bingli003” that contain the same business attributes in Table 1.
- order is implemented based on the number determined by the client. In other words, the sequence of user data records has been reflected in the index to a certain extent.
- the business attributes and numbers of the data records are determined, and the merge field containing the business attributes and numbers is generated, and the storage location in the ledger is established to establish the merge field Correspondence with location information, so as to realize that the number information specified by the user is included in the index.
- FIG. 5 is a schematic flowchart of a data query method based on the aforementioned index provided by an embodiment of this specification, including S501 to S505.
- S501 Receive a query instruction including service attributes.
- receiving a query request containing the specific value of a business attribute (generally, the query request can be sent in the form of an instruction).
- the inquiry request can come from the docking organization or the service user of the docking organization. Therefore, the database can perform matching from the index table according to the specific value of the business attribute. For example, after Table 1 is created, the user inputs a query command, Retrieve(bingli, &v, FULL) to the server through the client.
- S503 Perform matching from an index table according to the business attribute, and determine location information corresponding to each primary key containing the business attribute in the index table.
- the database server will first query all primary keys that contain business attributes. In the example in Table 1, you can get “bingli001”, “bingli003”, “bingli002”, etc., and determine each one in turn. The location information (2,08), (2,10), (3,99) and so on corresponding to the primary key.
- S505 Obtain corresponding data records from the ledger according to the location information, and return the obtained corresponding data records to the sender of the query instruction.
- the data records are read according to the order of the obtained primary keys, that is, the data records corresponding to the location information of "bingli001", “bingli003", and “bingli002" are read in sequence.
- the order of the data records obtained by the user will also be arranged according to the order "bingli001", “bingli003", and "bingli002" of the primary key in the index.
- the primary keys in the index table can be reordered according to the number. It is easy to understand that the primary keys at this time will be arranged in order. In this way, the order of the obtained data records will be in order according to the number. Arranged to meet the needs of users.
- the database server when the database server obtains the primary keys containing the business attributes in the instruction in the index table, it can also directly obtain the number from the primary key, and then based on the one-to-one correspondence between the primary key and the data record, Sort the data obtained by the query according to the serial number to obtain an ordered set of data records (that is, the data records are arranged in sequence according to the serial number contained in each data record), and return the ordered set of data records to the sender of the query instruction. In this way, even if the primary key has not been reordered in the index table, the sequential query of data records can be achieved.
- the user can also directly enter the query instruction that contains the number.
- the database server first needs to determine the corresponding primary key according to the number and business attributes.
- the query instruction contains only one number For example, retrieve(bingli,001,&v)
- the corresponding primary key can be determined to be "bingli001", so as to query the location information (2,08);
- the query instruction can also include one Or multiple numbering intervals, such as Retrieve(bingli, (001, 007), (100, 110), &v), so that it can be determined that the corresponding primary key is from “bingli001" to "bingli007", and, "bingli100” to "bingli110",
- it is still arranged according to the serial number. In this way, accurate and orderly query in the blockchain ledger can be realized.
- the embodiment of the specification also provides an index creation device, which is applied to a centralized database server that stores data through a block-chain ledger, as shown in FIG. 6, which is the embodiment of the specification.
- An index creation device provided includes the following modules.
- the obtaining module 601 obtains the business attributes and serial numbers contained in the data records, where the serial numbers are determined by the client.
- the position information determining module 603 determines the position information of the data record in the ledger.
- the position information includes the block height of the data block where the data record is located, and the offset in the data block where the data record is located.
- the generating module 605 generates a merge field containing business attributes and serial numbers.
- the writing module 607 establishes the corresponding relationship between the merge field and the location information, and writes the index with the merge field as the main key.
- the generating module 605 splices the serial number after the business attribute to generate a merged field containing the business attribute and the serial number.
- the generating module 605 sorts the merge fields according to the numbers included in the merge fields, and writes the merge fields in the index with the merge fields as the primary key in sequence.
- the device further includes a data block generation module 609, which receives the data records to be stored and determines the hash value of each data record.
- the hash value of the N data blocks and the Nth data block of each data record wherein the block height of the data block increases monotonically based on the sequence of the block time.
- the preset blocking condition includes: the number of data records to be stored reaches the number threshold; or, the time interval from the last blocking time reaches the time threshold.
- an embodiment of this specification also provides a query device based on the aforementioned index, as shown in FIG. 7, which is a schematic structural diagram of a query device provided by an embodiment of this specification, including the following modules.
- the instruction receiving module 701 receives a query instruction including business attributes.
- the matching module 703 is configured to perform matching from an index table according to the business attribute, and determine the location information corresponding to each primary key containing the business attribute in the index table.
- the data obtaining module 705 obtains corresponding data records from the ledger according to the location information, and returns the obtained corresponding data records to the sender of the query instruction.
- the device further includes a serial number determining module 707, which is used to determine, before obtaining the corresponding data record from the ledger according to the location information, the data in each primary key containing the business attribute in the index table.
- the data acquisition module 705 sorts the data records obtained by the query according to the number to generate an ordered set of data records; and returns the ordered set of data records to the sender of the query instruction .
- the instruction receiving module 701 receives a query instruction including business attributes and numbers; correspondingly, the matching module 703 performs matching from the index table according to the business attributes and numbers, and according to the business attributes and numbers The number determines the primary key, and the location information corresponding to the primary key determined by the business attribute and the number in the index table acquisition is determined.
- the embodiments of this specification also provide a computer device, which at least includes a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor implements the index shown in FIG. 4 when the program is executed. Create method.
- the embodiments of this specification also provide a computer device, which at least includes a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor implements the data shown in FIG. 5 when the program is executed. Query method.
- FIG. 8 shows a more specific hardware structure diagram of a computing device provided by an embodiment of this specification.
- the device may include a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050.
- the processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040 realize the communication connection between each other in the device through the bus 1050.
- the processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit, central processing unit), microprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits for execution related Program to realize the technical solutions provided in the embodiments of this specification.
- a general-purpose CPU Central Processing Unit, central processing unit
- microprocessor microprocessor
- application specific integrated circuit Application Specific Integrated Circuit, ASIC
- ASIC Application Specific Integrated Circuit
- the memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc.
- the memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, related program codes are stored in the memory 1020 and called and executed by the processor 1010.
- the input/output interface 1030 is used to connect an input/output module to realize information input and output.
- the input/output/module can be configured in the device as a component (not shown in the figure), or it can be connected to the device to provide corresponding functions.
- the input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc.
- an output device may include a display, a speaker, a vibrator, an indicator light, and the like.
- the communication interface 1040 is used to connect a communication module (not shown in the figure) to realize the communication interaction between the device and other devices.
- the communication module can realize communication through wired means (such as USB, network cable, etc.), or through wireless means (such as mobile network, WIFI, Bluetooth, etc.).
- the bus 1050 includes a path to transmit information between various components of the device (for example, the processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040).
- the above device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include the equipment necessary for normal operation. Other components.
- the above-mentioned device may also include only the components necessary to implement the solutions of the embodiments of the present specification, and not necessarily include all the components shown in the figures.
- the embodiment of this specification also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the index creation method shown in FIG. 4 is implemented.
- the embodiment of this specification also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the data query method shown in FIG. 5 is implemented.
- Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
- the information can be computer-readable instructions, data structures, program modules, or other data.
- Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
- a typical implementation device is a computer.
- the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, and a game control A console, a tablet computer, a wearable device, or a combination of any of these devices.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910993128.5 | 2019-10-18 | ||
CN201910993128.5A CN110825737A (zh) | 2019-10-18 | 2019-10-18 | 索引创建和数据查询方法、装置及设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021073242A1 true WO2021073242A1 (fr) | 2021-04-22 |
Family
ID=69549530
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/109289 WO2021073242A1 (fr) | 2019-10-18 | 2020-08-14 | Procédés, appareil et dispositif de création d'index et d'interrogation de données |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110825737A (fr) |
WO (1) | WO2021073242A1 (fr) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113568924A (zh) * | 2021-07-23 | 2021-10-29 | 北京达佳互联信息技术有限公司 | 一种数据处理方法、装置、电子设备及存储介质 |
CN113592447A (zh) * | 2021-07-29 | 2021-11-02 | 远光软件股份有限公司 | 电力现货市场的财务结算方法、装置、存储介质和电子设备 |
CN116126942A (zh) * | 2023-02-09 | 2023-05-16 | 国家气象信息中心(中国气象局气象数据中心) | 一种多维空间气象网格数据分布式存储查询方法及系统 |
CN117453682A (zh) * | 2023-09-26 | 2024-01-26 | 广州海量数据库技术有限公司 | 在openGauss数据库上并行创建列存表btree索引的方法和系统 |
US11947537B1 (en) * | 2020-12-01 | 2024-04-02 | Amazon Technologies, Inc. | Automatic index management for a non-relational database |
CN118069074A (zh) * | 2024-04-22 | 2024-05-24 | 联想凌拓科技有限公司 | 一种数据处理方法及装置、存储介质、计算机程序产品 |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110825737A (zh) * | 2019-10-18 | 2020-02-21 | 支付宝(杭州)信息技术有限公司 | 索引创建和数据查询方法、装置及设备 |
CN111339217B (zh) * | 2020-02-26 | 2023-10-27 | 慧择保险经纪有限公司 | 一种数据处理方法及装置 |
CN111581215B (zh) * | 2020-05-07 | 2020-12-15 | 钟士平 | 数组树数据储存方法、快速查找方法及可读储存介质 |
CN111444198B (zh) * | 2020-06-15 | 2020-09-25 | 支付宝(杭州)信息技术有限公司 | 一种基于中心化块链式账本的交易存储、查询方法 |
CN113379523A (zh) * | 2021-06-10 | 2021-09-10 | 北京京东振世信息技术有限公司 | 账单生成方法、装置、介质及电子设备 |
CN113656397A (zh) * | 2021-07-02 | 2021-11-16 | 阿里巴巴新加坡控股有限公司 | 一种针对时序数据的索引构建及查询的方法、装置 |
CN113535733A (zh) * | 2021-07-26 | 2021-10-22 | 北京锐安科技有限公司 | 数据存储、查询方法、装置、计算机设备及存储介质 |
CN114185890B (zh) * | 2021-12-09 | 2022-11-01 | 北京航星永志科技有限公司 | 一种数据库检索方法、装置、存储介质及电子设备 |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105740440A (zh) * | 2016-02-01 | 2016-07-06 | 上海凭安网络科技有限公司 | 一种加快区块链查询的索引方法 |
CN107273482A (zh) * | 2017-06-12 | 2017-10-20 | 北京市天元网络技术股份有限公司 | 基于HBase的告警数据存储方法及装置 |
US20190042620A1 (en) * | 2017-08-01 | 2019-02-07 | International Business Machines Corporation | Optimizing queries and other retrieve operations in a blockchain |
CN109902086A (zh) * | 2019-01-31 | 2019-06-18 | 阿里巴巴集团控股有限公司 | 一种索引创建方法、装置及设备 |
WO2019141289A2 (fr) * | 2019-05-14 | 2019-07-25 | Alibaba Group Holding Limited | Procédé et dispositif pour traversée de données |
CN110162526A (zh) * | 2019-04-18 | 2019-08-23 | 阿里巴巴集团控股有限公司 | 一种块链式账本中数据记录的查询方法、装置及设备 |
CN110825737A (zh) * | 2019-10-18 | 2020-02-21 | 支付宝(杭州)信息技术有限公司 | 索引创建和数据查询方法、装置及设备 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102880705B (zh) * | 2012-09-28 | 2015-09-02 | 用友软件股份有限公司 | 数据库主键生成装置和数据库主键生成方法 |
US10725987B2 (en) * | 2014-11-25 | 2020-07-28 | Sap Se | Forced ordering of a dictionary storing row identifier values |
CN106709851B (zh) * | 2016-11-30 | 2021-07-09 | 中体彩科技发展有限公司 | 大数据检索方法及装置 |
CN113726751B (zh) * | 2019-03-26 | 2023-08-18 | 创新先进技术有限公司 | 一种块链式账本中的权重管理方法、装置及设备 |
CN110162662B (zh) * | 2019-04-18 | 2023-02-28 | 创新先进技术有限公司 | 一种块链式账本中数据记录的验证方法、装置及设备 |
CN110188096B (zh) * | 2019-04-18 | 2021-08-17 | 创新先进技术有限公司 | 一种数据记录的索引创建方法、装置及设备 |
-
2019
- 2019-10-18 CN CN201910993128.5A patent/CN110825737A/zh active Pending
-
2020
- 2020-08-14 WO PCT/CN2020/109289 patent/WO2021073242A1/fr active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105740440A (zh) * | 2016-02-01 | 2016-07-06 | 上海凭安网络科技有限公司 | 一种加快区块链查询的索引方法 |
CN107273482A (zh) * | 2017-06-12 | 2017-10-20 | 北京市天元网络技术股份有限公司 | 基于HBase的告警数据存储方法及装置 |
US20190042620A1 (en) * | 2017-08-01 | 2019-02-07 | International Business Machines Corporation | Optimizing queries and other retrieve operations in a blockchain |
CN109902086A (zh) * | 2019-01-31 | 2019-06-18 | 阿里巴巴集团控股有限公司 | 一种索引创建方法、装置及设备 |
CN110162526A (zh) * | 2019-04-18 | 2019-08-23 | 阿里巴巴集团控股有限公司 | 一种块链式账本中数据记录的查询方法、装置及设备 |
WO2019141289A2 (fr) * | 2019-05-14 | 2019-07-25 | Alibaba Group Holding Limited | Procédé et dispositif pour traversée de données |
CN110825737A (zh) * | 2019-10-18 | 2020-02-21 | 支付宝(杭州)信息技术有限公司 | 索引创建和数据查询方法、装置及设备 |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11947537B1 (en) * | 2020-12-01 | 2024-04-02 | Amazon Technologies, Inc. | Automatic index management for a non-relational database |
CN113568924A (zh) * | 2021-07-23 | 2021-10-29 | 北京达佳互联信息技术有限公司 | 一种数据处理方法、装置、电子设备及存储介质 |
CN113568924B (zh) * | 2021-07-23 | 2024-05-14 | 北京达佳互联信息技术有限公司 | 一种数据处理方法、装置、电子设备及存储介质 |
CN113592447A (zh) * | 2021-07-29 | 2021-11-02 | 远光软件股份有限公司 | 电力现货市场的财务结算方法、装置、存储介质和电子设备 |
CN116126942A (zh) * | 2023-02-09 | 2023-05-16 | 国家气象信息中心(中国气象局气象数据中心) | 一种多维空间气象网格数据分布式存储查询方法及系统 |
CN116126942B (zh) * | 2023-02-09 | 2023-11-24 | 国家气象信息中心(中国气象局气象数据中心) | 一种多维空间气象网格数据分布式存储查询方法 |
CN117453682A (zh) * | 2023-09-26 | 2024-01-26 | 广州海量数据库技术有限公司 | 在openGauss数据库上并行创建列存表btree索引的方法和系统 |
CN118069074A (zh) * | 2024-04-22 | 2024-05-24 | 联想凌拓科技有限公司 | 一种数据处理方法及装置、存储介质、计算机程序产品 |
Also Published As
Publication number | Publication date |
---|---|
CN110825737A (zh) | 2020-02-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021073242A1 (fr) | Procédés, appareil et dispositif de création d'index et d'interrogation de données | |
WO2020211569A1 (fr) | Procédé de construction d'index d'enregistrement de données | |
WO2021017422A1 (fr) | Procédé de création d'index dans un livre de comptes de type à chaîne de blocs, dispositif et appareil | |
CN110188096B (zh) | 一种数据记录的索引创建方法、装置及设备 | |
WO2020244239A1 (fr) | Procédé, appareil et dispositif de création d'indice basés sur un identifiant de service | |
CN110162526B (zh) | 一种块链式账本中数据记录的查询方法、装置及设备 | |
CN110162662B (zh) | 一种块链式账本中数据记录的验证方法、装置及设备 | |
WO2020253231A1 (fr) | Procédé et appareil de stockage de données à base de reçu, et dispositif | |
WO2021093461A1 (fr) | Procédé et appareil de calcul d'agrégation dans un registre de chaîne de blocs, et dispositif | |
WO2021057164A1 (fr) | Procédé et dispositif d'interrogation pour un registre de chaîne de blocs et appareil | |
WO2020233146A1 (fr) | Procédé, système et appareil de stockage d'enregistrement d'opération de données, et dispositif | |
WO2021073240A1 (fr) | Procédé, dispositif et appareil pour stocker des données dans un registre de blockchain | |
US10795874B2 (en) | Creating index in blockchain-type ledger | |
WO2020244237A1 (fr) | Procédé, dispositif et appareil de vérification de registre de chaîne de blocs | |
WO2021073241A1 (fr) | Procédé et dispositif de lecture de données basés sur un stockage sur disque, et appareil | |
US11816099B2 (en) | Service identifier-based data indexing | |
US11126751B2 (en) | Index creation for data records | |
WO2021057127A1 (fr) | Procédé, dispositif et équipement de stockage de données sur la base de multiples attributs de service | |
CN110334094B (zh) | 一种基于倒排索引的数据查询方法、系统、装置及设备 | |
US11005648B2 (en) | Blockchain-type data storage | |
WO2021093462A1 (fr) | Procédé et appareil de mémorisation d'enregistrement d'opération dans une base de données, et dispositif | |
CN110362570B (zh) | 一种数据存储方法、装置及设备 | |
CN111444194B (zh) | 一种块链式账本中索引的清除方法、装置及设备 | |
CN110636042B (zh) | 一种服务端已验证块高的更新方法、装置及设备 | |
CN111444195B (zh) | 一种块链式账本中索引的清除方法、装置及设备 |
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: 20876902 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: 20876902 Country of ref document: EP Kind code of ref document: A1 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20876902 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 13.10.2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20876902 Country of ref document: EP Kind code of ref document: A1 |