Data storage method, device, computer storage medium and computer program product

Abstract

The application provides a data storage method, device, computer storage medium and computer program product. The method comprises the following steps: after obtaining to-be-stored data, determining element data corresponding to each index item element of the to-be-stored data according to a preset index item element template, generating an index item containing the element data corresponding to each index item element of the to-be-stored data, obtaining a target index item corresponding to the to-be-stored data, and storing data contained in the target index item based on a preset non-relational data storage structure. The application dynamically constructs the index item of the to-be-stored data corresponding to multiple element dimensions, and stores the target index item by using the non-relational data storage structure, which can effectively solve the problems of the traditional relational database storage mode, such as difficult index storage, difficult query, inability to dynamically support index attribute expansion, difficulty in dynamically adding tables, and difficulty in maintaining, can regularize the index data base of the user, and better supports the construction of a business system.

Description

Technical Field

[0001] This application belongs to the field of data storage technology, and in particular relates to a data storage method, apparatus, computer storage medium, and computer program product. Background Technology

[0002] Business systems typically provide a large amount of indicator data for spatial or data calculations, and display the statistical and calculation results to users, or use it as the foundational data of the system to provide data support for the system.

[0003] Traditionally, relational databases (such as Oracle and MySQL) are used to store indicator data. However, this method has complex storage logic, low calculation and rendering efficiency, and leads to a series of problems such as difficulty in storing and querying indicator data, inability to dynamically support indicator attribute expansion, and difficulty in maintaining dynamically added tables. Summary of the Invention

[0004] In view of this, this application provides a data storage method, apparatus, computer storage medium, and computer program product to solve at least some of the shortcomings of traditional relational database storage methods, such as difficulty in index entry, difficulty in querying, and inability to dynamically support index attribute expansion, thereby standardizing the user's index data foundation and better supporting the construction of business systems.

[0005] The specific plan is as follows:

[0006] A data storage method, comprising:

[0007] Retrieve the data to be stored;

[0008] According to the preset indicator item element template, determine the element data corresponding to each indicator item element of the data to be stored;

[0009] Generate an indicator item containing element data corresponding to each indicator item element of the data to be stored, and obtain the target indicator item corresponding to the data to be stored;

[0010] The data contained in the target indicator item is stored based on a preset non-relational data storage structure.

[0011] Optionally, determining the element data corresponding to each indicator element of the data to be stored according to a preset indicator element template includes:

[0012] According to the preset indicator item element template, extract the element data of the data to be stored that corresponds to at least some of the elements in the indicator basic attributes, indicator dimensions, indicator values, and calculation rules.

[0013] The indicator dimension is used to describe indicator information from the perspective of specific features. The basic attributes of the indicator are constructed based on pre-configured metadata and dictionary tables. The metadata is used to indicate the basic attributes required for the indicator item. The dictionary table is used to store the keywords under different indicator dimensions and / or different basic attributes required for different indicator items.

[0014] Optionally, the data contained in the target indicator item is stored based on a preset non-relational data storage structure, including:

[0015] Based on the multiple different hierarchical nodes preset in the document-oriented non-relational database storage structure, the identifier of the target indicator item, the indicator item elements contained in the target indicator item, and the element data corresponding to each indicator item element are stored hierarchically.

[0016] Based on the preset relational nodes in the document-type non-relational database storage structure, the association relationships between different levels of nodes corresponding to the target indicator items are stored.

[0017] Optionally, the method further includes:

[0018] When storing the data contained in the target indicator item, the target indicator item and its related indicator items are organized into corresponding directories for storage.

[0019] Optionally, organizing the target indicator item and its related indicator items into corresponding directories for storage includes:

[0020] The hierarchical storage structure corresponding to the target indicator item is attached to the corresponding system node of the indicator system to which the target indicator item belongs, so as to organize the target indicator item and each existing indicator item in the indicator system into a corresponding directory for storage.

[0021] Among them, each existing indicator item in the indicator system is an indicator item related to the target indicator item.

[0022] Optionally, the various hierarchical nodes include table nodes, field nodes, and field value description nodes with progressively lower hierarchical levels.

[0023] Optionally, the method further includes:

[0024] Add corresponding validation rules to the relevant keywords in the dictionary table, and validate the numerical values ​​of the keywords based on the corresponding validation rules.

[0025] A data storage device, comprising:

[0026] The acquisition unit is used to acquire data to be stored.

[0027] The determining unit is used to determine the element data corresponding to each indicator element of the data to be stored according to a preset indicator element template.

[0028] The generation unit is used to generate indicator items containing element data corresponding to each indicator item element of the data to be stored, thereby obtaining the target indicator item corresponding to the data to be stored.

[0029] A storage unit is used to store the data contained in the target indicator item based on a preset non-relational data storage structure.

[0030] A computer-readable medium having a computer program stored thereon, the computer program comprising program code for performing the methods described in any of the preceding descriptions.

[0031] A computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods described in any of the preceding descriptions.

[0032] In summary, the data storage method, apparatus, computer storage medium, and computer program product provided in this application, after obtaining the data to be stored, determine the element data corresponding to each indicator element of the data to be stored according to a preset indicator element template, generate indicator items containing the element data corresponding to each indicator element of the data to be stored, obtain the target indicator item corresponding to the data to be stored, and store the data contained in the target indicator item based on a preset non-relational data storage structure. This application, by dynamically constructing multi-element dimension indicator items corresponding to the data to be stored and using a non-relational data storage structure to store the target indicator items, can effectively solve the problems of difficulty in indicator entry and querying, inability to dynamically support indicator attribute expansion, and difficulty in maintaining dynamically added tables that exist in traditional relational database storage methods. It can standardize the user's indicator data foundation and better support the construction of business systems. Attached Figure Description

[0033] The above and other features, advantages, and aspects of the embodiments of this application will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0034] Figure 1 This is a flowchart illustrating the data storage method provided in this application;

[0035] Figure 2 This is an exemplary functional interface for dictionary management provided in this application;

[0036] Figure 3 These are examples of keywords in the time granularity dimension of dictionary management provided in this application;

[0037] Figure 4 This is an exemplary management function interface for the keyword "year" in the time granularity dimension provided in this application;

[0038] Figure 5 This is an exemplary functional interface for constructing basic attributes of indicator items based on metadata management functions provided in this application;

[0039] Figure 6 This is an example of extracting the data of each indicator element of the data to be stored based on the indicator element template provided in this application;

[0040] Figure 7 This is an example of storing indicator items / indicator systems in a non-relational data storage structure, as provided in this application;

[0041] Figure 8 This is a structural diagram of the data storage device provided in this application. Detailed Implementation

[0042] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While some embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this application. It should be understood that the drawings and embodiments of this application are for illustrative purposes only and are not intended to limit the scope of protection of this application.

[0043] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0044] It should be noted that the concepts of "first" and "second" mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0045] It should be noted that the terms "a" and "a plurality of" used in this application are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0046] This application provides a data storage method, apparatus, computer storage medium, and computer program product, which solves the problems of difficulty in index storage, difficulty in querying, and inability to dynamically support index attribute expansion in traditional relational database storage methods by proposing and implementing a scheme for index data storage based on a non-relational data storage structure. This aims to standardize the user's index data foundation and better support the construction of business systems.

[0047] See Figure 1 The data storage method flowchart shown in this application includes the following processing flow:

[0048] Step 101: Obtain the data to be stored.

[0049] The data to be stored can be, but is not limited to, the indicator data to be stored provided by the business system. Specifically, it can be the relevant indicator data used for spatial calculation or data calculation, or the relevant indicator data used as the system's foundation information to provide data support for the system. There are no restrictions.

[0050] The data to be stored is specifically unstructured indicator data, for example, such as: [Urbanization rate of permanent residents in **City, the long-term target value for 2035 is 75%], [Service coverage rate within 800 meters of rail transit stations: xxx], etc.

[0051] Step 102: According to the preset indicator item element template, determine the element data corresponding to each indicator item element of the data to be stored.

[0052] This application proposes and defines the following series of basic concepts in advance to support the storage of index data based on a non-relational data storage structure:

[0053] Dictionary management, metadata, indicator dimensions, indicator items, indicator system, indicator values.

[0054] Among them, dictionary management is used to solve the problem of storing and managing dictionary values ​​of indicator data. It stores keywords such as unit, time, region and other dimensions or custom dimensions that need to be used for each indicator item through dictionary tables. It can also store and manage keywords under the basic attributes of each indicator item.

[0055] Optionally, dictionary management also supports adding corresponding validation rules for the corresponding keywords in the dictionary table, so as to support the validation of the numerical values ​​of the corresponding keywords based on the validation rules.

[0056] See Figure 2 It provides an exemplary functional interface for dictionary management, including but not limited to keyword configuration, storage, and management functions based on various dimensions such as measurement units, time granularity, regional division, land use classification, business, and functions.

[0057] like Figure 3 As shown, examples of each keyword at the time granularity dimension are further provided. Figure 4 It provides a management interface for the keyword "year" field under the time granularity dimension. Based on the management functions corresponding to this interface, it is possible to dynamically display relevant information of the "year" unit field under the unit dimension of the indicator value.

[0058] Metadata is used to construct the basic attributes of indicator items. Specifically, the construction and maintenance of these basic attributes can be performed through corresponding metadata management functions, such as... Figure 5 As shown, this enables the dynamic construction of indicator items.

[0059] Indicator dimensions are used to describe indicator information from a specific feature perspective, describing what attributes the indicator has in the corresponding feature perspective / dimension.

[0060] An indicator item is the basic unit of an indicator. An indicator value is the value associated with different indicator dimensions based on the indicator item.

[0061] For example, the indicator for the urbanization rate of permanent residents in **City is 75% by 2035. This data includes the spatial dimension of **City, the time dimension of the target value for 2035, and the indicator value of 75%, in the unit of % (%).

[0062] An indicator system is used to organize the indicator items that need to be associated into a directory. Different business systems may have different indicator items to be calculated and their corresponding indicator values, which can be defined through an indicator system.

[0063] Based on the aforementioned series of fundamental concepts, the constituent elements of an indicator item are further defined. An indicator item includes an indicator value as its constituent element. In addition, it may include, but is not limited to, basic attributes, dimensions, and calculation rules. Attributes are constructed using a dictionary table and metadata. Basic attributes can include fixed attributes and dynamically extended attributes to support the dynamic expansion of indicator item attributes by dynamically adding required attribute fields.

[0064] To facilitate the dynamic construction of corresponding indicator items for the data to be stored, this application embodiment pre-defines an indicator item element template that provides each component element of the indicator item. After obtaining the data to be stored, the element data corresponding to each indicator item element in the template can be extracted based on this template, such as extracting the element data corresponding to each indicator element, including basic indicator attributes, indicator dimensions, indicator values, calculation rules, etc. See also... Figure 6It provides an example of extracting the data of each indicator element of the data to be stored, such as "Service coverage rate within 800 meters of rail transit stations: xxx", based on the indicator element template.

[0065] Step 103: Generate indicator items containing element data corresponding to each indicator item element of the data to be stored, and obtain the target indicator items corresponding to the data to be stored.

[0066] After extracting the data of each indicator element of the data to be stored based on the indicator element template, the target indicator corresponding to the data to be stored can be generated. The generated target indicator contains the element data of each component of the data to be stored, such as the basic attributes, indicator dimensions, indicator values, calculation rules, etc. of the data to be stored.

[0067] Step 104: Based on the preset non-relational data storage structure, store the data contained in the target indicator item.

[0068] Optionally, this application adopts a document-based non-relational database storage structure to store the data contained in the target indicator items. That is, in this embodiment of the application, the non-relational data storage structure is a document-based non-relational database storage structure.

[0069] This application pre-defines various hierarchical nodes in a document-oriented non-relational database storage structure, including but not limited to table nodes, field nodes, and field value description nodes with descending hierarchical levels. Table nodes are set up for multiple data objects, which refer to objects containing various types of data, such as but not limited to indicator systems, indicator items, dictionaries, etc. Field nodes are set up for indicator attributes, indicator dimensions, or keyword fields under dictionary tables. Field value description nodes are used to store the values ​​corresponding to the fields.

[0070] Meanwhile, a relation node is pre-defined in the document-oriented non-relational database storage structure to store the relationships between indicator systems, indicator items, basic attributes, dimensions, dictionaries, etc., including but not limited to relationships such as contain, own, belong to, and depend. For example, an indicator system contains an indicator item and its corresponding system version, an indicator system belongs to a certain system type, an indicator item has certain indicator value types, an indicator item has certain attributes, an attribute is built based on certain metadata, a certain metadata depends on a certain dictionary, and so on.

[0071] Accordingly, after obtaining the target indicator items corresponding to the data to be stored, this application stores the identifier of the target indicator item, the indicator item elements contained in the target indicator item, and the element data corresponding to each indicator item element in a hierarchical manner based on different levels of nodes such as tables, fields, and field value descriptions preset in the document-type non-relational database storage structure. In addition, it also stores the association relationship between different levels of nodes corresponding to the target indicator item based on preset relational nodes, thereby realizing the dynamic construction of indicator items for the data to be stored and the non-relational data structure storage of the constructed indicator items.

[0072] For example, the target indicator item is first constructed as a table node to store the identifier of the target indicator item. Then, multiple field nodes are used to store different keyword fields under each basic attribute / dimension of the target indicator item, and multiple field value description nodes are used to store the values ​​of different keyword fields. Furthermore, the relationship between the nodes corresponding to each level of the target indicator item is constructed and stored based on the relationship nodes, such as the relationship between the table node and the field nodes under each attribute / dimension, and the relationship between each field node and the field value description node. In addition, the dependency relationship between attributes and metadata, dictionaries, etc. can be further constructed.

[0073] Alternatively, when storing the data contained in the target indicator, the target indicator and its related indicators can be organized into corresponding directories for storage.

[0074] Specifically, this can be achieved by attaching the hierarchical storage structure corresponding to the target indicator item to the corresponding system node of its own indicator system, thereby organizing the target indicator item and the existing indicator items in its own indicator system into corresponding directories for storage; it is easy to understand that the existing indicator items in the indicator system to which the target indicator item belongs constitute the indicator items related to the target indicator item.

[0075] See Figure 7 This paper provides an example of storing indicator items and indicator systems based on the aforementioned non-relational data storage structure. Compared with traditional relational database storage methods, the non-relational data storage structure provided in this application embodiment is more conducive to the input and query of indicators. It also supports the dynamic expansion of indicator item attributes by dynamically adding required attribute fields to the indicator item element template, and allows for the dynamic addition and maintenance of database tables by attaching required tables to the non-relational database storage structure document. This effectively solves the problems of difficulty in inputting and querying indicators, inability to dynamically support indicator attribute expansion, and difficulty in maintaining dynamically added tables in traditional relational databases.

[0076] In summary, the data storage method provided in this application, after obtaining the data to be stored, determines the element data corresponding to each indicator element of the data to be stored according to a preset indicator element template, generates an indicator item containing the element data corresponding to each indicator element of the data to be stored, obtains the target indicator item corresponding to the data to be stored, and stores the data contained in the target indicator item based on a preset non-relational data storage structure. This application, by dynamically constructing multi-element dimension indicator items corresponding to the data to be stored and using a non-relational data storage structure to store the target indicator item, can effectively solve the problems of difficulty in indicator entry and querying, inability to dynamically support indicator attribute expansion, and difficulty in maintaining dynamically added tables that exist in traditional relational database storage methods. It can standardize the user's indicator data foundation and better support the construction of business systems.

[0077] Corresponding to the above-described data storage method, this application also provides a data storage device, the structure of which is as follows: Figure 8 As shown, it includes:

[0078] Acquisition unit 10 is used to acquire data to be stored;

[0079] The determining unit 20 is used to determine the element data corresponding to each indicator element of the data to be stored according to the preset indicator element template.

[0080] The generation unit 30 is used to generate an index item containing element data corresponding to each index item element of the data to be stored, so as to obtain the target index item corresponding to the data to be stored.

[0081] Storage unit 40 is used to store the data contained in the target indicator item based on a preset non-relational data storage structure.

[0082] In one embodiment, the determining unit 20 is specifically used for:

[0083] According to the preset indicator item element template, extract the element data of the data to be stored that corresponds to at least some of the elements in the indicator basic attributes, indicator dimensions, indicator values, and calculation rules.

[0084] The indicator dimension is used to describe indicator information from the perspective of specific features. The basic attributes of the indicator are constructed based on pre-configured metadata and dictionary tables. The metadata is used to indicate the basic attributes required for the indicator item. The dictionary table is used to store the keywords under different indicator dimensions and / or different basic attributes required for different indicator items.

[0085] In one embodiment, the storage unit 40 is specifically used for:

[0086] Based on the multiple different hierarchical nodes preset in the document-oriented non-relational database storage structure, the identifier of the target indicator item, the indicator item elements contained in the target indicator item, and the element data corresponding to each indicator item element are stored hierarchically.

[0087] Based on the preset relational nodes in the document-type non-relational database storage structure, the association relationships between different levels of nodes corresponding to the target indicator items are stored.

[0088] In one embodiment, the storage unit 40 is further configured to:

[0089] When storing the data contained in the target indicator item, the target indicator item and its related indicator items are organized into corresponding directories for storage.

[0090] In one embodiment, the storage unit 40, when organizing the target indicator item and its related indicator items into corresponding directories for storage, is specifically used for:

[0091] The hierarchical storage structure corresponding to the target indicator item is attached to the corresponding system node of the indicator system to which the target indicator item belongs, so as to organize the target indicator item and each existing indicator item in the indicator system into a corresponding directory for storage.

[0092] Among them, each existing indicator item in the indicator system is an indicator item related to the target indicator item.

[0093] In one embodiment, the various hierarchical nodes include table nodes, field nodes, and field value description nodes in descending order of hierarchy.

[0094] In one embodiment, the above-mentioned apparatus further includes: a rule configuration unit, used to add corresponding verification rules for corresponding keywords in the dictionary table, so as to verify the value of the keywords based on the corresponding verification rules.

[0095] The data storage device provided in this application is described simply because it corresponds to the data storage method provided in the above method embodiments. For any similarities, please refer to the description of the above method embodiments, which will not be detailed here.

[0096] This application also provides a computer-readable medium having a computer program stored thereon, the computer program comprising program code for performing the data storage method as provided in the above method embodiments.

[0097] In the context of this application, a computer-readable medium (machine-readable medium) can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0098] It should be noted that the computer-readable medium described above in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0099] The aforementioned computer-readable medium may be contained within an electronic device or may exist independently without being assembled into an electronic device.

[0100] This application also provides a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the data storage method as provided in the above method embodiments.

[0101] Specifically, according to embodiments of this application, the processes described in the above-described reference flowcharts can be implemented as computer software programs. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, it performs the functions defined in the methods of the embodiments of this application.

[0102] It should be noted that although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

[0103] While several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this application. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0104] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described application concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions claimed in this application.

Claims

1. A data storage method, characterized by, The method comprises the following steps: obtaining to-be-stored data; extracting element data corresponding to elements in index basic attributes, index dimensions, index values and calculation rules of the to-be-stored data according to a preset index item element template; wherein the index dimensions are used for describing index information from a feature perspective, the index basic attributes are constructed based on pre-configured metadata and a dictionary table, the metadata are used for indicating basic attributes required by an index item, and the dictionary table is used for storing keywords required by different index dimensions and / or different basic attributes corresponding to different index items; generating an index item containing element data corresponding to each index item element of the to-be-stored data to obtain a target index item corresponding to the to-be-stored data, wherein the generated target index item contains element data of each component element of the to-be-stored data; storing, based on a plurality of different hierarchical nodes preset in a document type non-relational database storage structure, an identifier of the target index item, each index item element contained in the target index item, and element data corresponding to each index item element; the plurality of different hierarchical nodes include table nodes, field nodes and field value description nodes in a hierarchical order from high to low; storing, based on a relationship node preset in the document type non-relational database storage structure, an association relationship between different hierarchical nodes corresponding to the target index item; when storing data contained in the target index item, hanging the hierarchical storage structure corresponding to the target index item under a corresponding system node of an index system to which the target index item belongs, so as to store the target index item and each existing index item in the index system to which the target index item belongs in a corresponding directory; wherein each existing index item in the index system is an index item related to the target index item.

2. The method of claim 1, wherein, Further comprising: adding a corresponding verification rule to a corresponding keyword in the dictionary table, so as to verify a numerical value of the keyword based on the corresponding verification rule.

3. A data storage device, characterized by The method comprises the following steps: an obtaining unit is configured to obtain to-be-stored data; a determining unit is configured to extract element data corresponding to elements in index basic attributes, index dimensions, index values and calculation rules of the to-be-stored data according to a preset index item element template; wherein the index dimensions are used for describing index information from a feature perspective, the index basic attributes are constructed based on pre-configured metadata and a dictionary table, the metadata are used for indicating basic attributes required by an index item, and the dictionary table is used for storing keywords required by different index dimensions and / or different basic attributes corresponding to different index items; a generating unit is configured to generate an index item containing element data corresponding to each index item element of the to-be-stored data to obtain a target index item corresponding to the to-be-stored data, wherein the generated target index item contains element data of each component element of the to-be-stored data. The storage unit is used to hierarchically store the identifier of the target indicator item, the indicator items included in the target indicator item, and the element data corresponding to each indicator item element, based on multiple different hierarchical nodes preset in the document-oriented non-relational database storage structure. The multiple different hierarchical nodes include table nodes, field nodes, and field value description nodes in descending order of hierarchy. Based on the pre-set relational nodes in the document-oriented non-relational database storage structure, the unit stores the association relationships between different hierarchical nodes corresponding to the target indicator item. When storing the data included in the target indicator item, the hierarchical storage structure corresponding to the target indicator item is attached to the corresponding system node of the indicator system to which the target indicator item belongs, so as to organize the target indicator item and its existing indicator items in the indicator system into corresponding directories for storage. The existing indicator items in the indicator system are indicator items related to the target indicator item.

4. A computer readable medium characterized by It stores a computer program thereon, the computer program containing program code for performing the method as described in any one of claims 1-2.

5. A computer program product, characterised in that, It includes a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the method as described in any one of claims 1-2.

Images