A query system and method

Abstract

This invention discloses a query system and method. The system includes a platform front-end layer, a data storage layer, and an indicator management layer. The indicator management layer includes an indicator parsing unit. The platform front-end layer is used to call a metadata interface service to obtain metadata, assemble the metadata based on query information input by the user terminal, generate query condition data corresponding to the query information, and send the query condition data to the indicator parsing unit. The indicator parsing unit is used to determine the target storage medium for the query result data corresponding to the query condition data based on a pre-established storage mapping relationship between the storage medium and platform data, generate a query instruction based on the target instruction requirements of the target storage medium and the query condition data, and send the query instruction to the data storage layer. The data storage layer is used to obtain the query result data from the target storage medium based on the received query instruction and feed the query result data back to the user terminal.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of online analytical processing technology, and in particular to a query system and method. Background Technology

[0002] With the emergence of big data, OLAP (Online Analytical Processing) platforms have been widely adopted by enterprises.

[0003] Currently, most OLAP platforms rely on one or more storage media for data storage and retrieval. During data storage, different storage media are selected based on the data information. During data retrieval, users typically need to first determine the storage media for the data being queried, and then input query commands according to the query syntax corresponding to that storage media to obtain the required data.

[0004] However, existing query methods require users to know the underlying data storage medium and storage format, which brings inconvenience to the data query process, reduces query efficiency, and results in a poor user experience. Summary of the Invention

[0005] This invention provides a query system and method to improve query efficiency and accuracy, and enhance user experience.

[0006] In a first aspect, embodiments of the present invention provide a query system, comprising: a platform front-end layer, a data storage layer, and an indicator management layer that is communicatively connected to the platform front-end layer and the data storage layer respectively; wherein, the indicator management layer includes an indicator parsing unit;

[0007] The platform front-end layer is used to call the metadata interface service to obtain metadata, assemble the metadata based on the query information input by the user terminal, generate query condition data corresponding to the query information, and send the query condition data to the indicator parsing unit.

[0008] The indicator parsing unit is used to determine the target storage medium for the query result data corresponding to the query condition data based on the pre-established storage mapping relationship between the storage medium and the platform data, generate a query instruction based on the target instruction requirements of the target storage medium and the query condition data, and send the query instruction to the data storage layer.

[0009] The data storage layer is used to retrieve query result data from the target storage medium based on the received query command and then feed the query result data back to the user terminal.

[0010] Secondly, embodiments of the present invention also provide a query method applied to a query system, the query system including a platform front-end layer, a data storage layer, and an indicator management layer communicatively connected to the platform front-end layer and the data storage layer respectively; wherein, the indicator management layer includes an indicator parsing unit; the method includes:

[0011] The platform front-end layer calls the metadata interface service to obtain metadata, assembles the metadata based on the query information input by the user terminal, generates query condition data corresponding to the query information, and sends the query condition data to the indicator parsing unit.

[0012] Based on the pre-established storage mapping relationship between the storage medium and the platform data, the indicator analysis unit determines the target storage medium for the query result data corresponding to the query condition data. Based on the target instruction requirements of the target storage medium and the query condition data, a query instruction is generated and sent to the data storage layer.

[0013] Based on the received query command, the data storage layer retrieves the query result data from the target storage medium and then feeds the query result data back to the user terminal.

[0014] The query system provided in this invention retrieves metadata by calling a metadata interface service through the platform front-end layer. Based on the query information input by the user terminal, the metadata is assembled to generate query condition data corresponding to the query information. An indicator parsing unit determines the target storage medium for the query result data corresponding to the query condition data based on a pre-established storage mapping relationship between the storage medium and platform data. Based on the target instruction requirements of the target storage medium and the query condition data, a query instruction is generated, enabling the data storage layer to retrieve the query result data from the target storage medium based on the query instruction, thus completing the data query process. This eliminates the need for the user to know the underlying data storage medium in advance or to manually write query instructions, thereby improving query efficiency and accuracy and enhancing the user experience.

[0015] Furthermore, the query method provided by this invention corresponds to the above-mentioned method and has the same beneficial effects. Attached Figure Description

[0016] To more clearly illustrate the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 A structural diagram of a query system provided in an embodiment of the present invention;

[0018] Figure 2 A schematic diagram of a query interface provided in an embodiment of the present invention;

[0019] Figure 3 A structural diagram of another query system provided in an embodiment of the present invention;

[0020] Figure 4 This is a schematic diagram of the overall architecture of a query system provided in an embodiment of the present invention;

[0021] Figure 5 This is a flowchart of a query method provided in an embodiment of the present invention. Detailed Implementation

[0022] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0023] Before discussing the exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but it may also have additional steps not included in the figures. The process may correspond to a method, function, procedure, subroutine, subroutine, etc.

[0024] To enable those skilled in the art to better understand the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0025] Example 1

[0026] Figure 1 This is a structural diagram of a query system provided in an embodiment of the present invention. Figure 1 As shown, the system in this embodiment may specifically include: a platform front-end layer 10, a data storage layer 12, and an indicator management layer 11 that is communicatively connected to the platform front-end layer 10 and the data storage layer 12, respectively; wherein, the indicator management layer 11 includes an indicator parsing unit 110;

[0027] The platform front-end layer 10 is used to call the metadata interface service to obtain metadata, assemble the metadata based on the query information input by the user terminal, generate query condition data corresponding to the query information, and send the query condition data to the indicator parsing unit 110.

[0028] The indicator parsing unit 110 is used to determine the target storage medium of the query result data corresponding to the query condition data based on the storage mapping relationship between the pre-established storage medium and the platform data, generate a query instruction based on the target instruction requirements of the target storage medium and the query condition data, and send the query instruction to the data storage layer 12.

[0029] Data storage layer 12 is used to retrieve query result data from the target storage medium based on the received query command, and to feed the query result data back to the user terminal.

[0030] The metadata interface service is a service for querying and extracting metadata. Users can call metadata through the metadata interface service according to different business needs. Metadata can be data that describes the attribute information of data in the system, which is used to support functions such as storage location, historical data, resource search and file records.

[0031] In this embodiment, users can input query information through the interface displayed on the user terminal. Figure 2 This is a schematic diagram of a query interface provided in an embodiment of the present invention, such as... Figure 2 As shown, the current user selects conditions for "Membership Status". The input query information can be "Membership information of valid members in the film and television business line with an expiration time of more than 30 days".

[0032] In practical implementation, the platform front-end layer 10 can obtain metadata through the metadata interface service, receive query information input by the user terminal, and determine the metadata corresponding to the query information from each metadata. Furthermore, according to the information relationships in the query information, the metadata corresponding to the query information can be assembled, and the assembled data can be determined as the query condition data.

[0033] It should be noted that the information relationship can be an SUM / OR relationship between conditions, or a sequential relationship between query conditions. For example, in the query "Member information of valid members in the film and television business line with an expiration time greater than 30 days", the information relationship is "SUM / OR"; while in the query "Users in the film and television business line who have paid for membership but have not continued to pay", the information relationship is sequential. It is necessary to assemble the metadata according to the information relationship reflected in the query information.

[0034] In this embodiment, the indicator parsing unit 110 can store the storage mapping relationship between platform data and storage media. Through the storage mapping relationship, the storage media corresponding to the platform data can be determined. After receiving the query condition data, the indicator parsing unit 110 can determine the target storage media of the query result data based on the storage mapping relationship. The query result data can be data that meets the query conditions. It should be noted that different storage media have different query syntaxes; the target instruction requirement is the query syntax requirement of the target storage media, and a corresponding query instruction can be generated based on the target instruction requirement and the query condition data.

[0035] Furthermore, the data storage layer 12 can receive query instructions sent by the index parsing unit 110, and through the instruction syntax of the query instructions, determine the target storage medium that the query instructions want to access, and then obtain the query result data corresponding to the query instructions in the target storage medium; and can feed back the query result data to the user terminal and display it on the query interface of the user terminal.

[0036] For example, the storage medium includes at least one of the following: Druid database connection pool, Clinkhouse (Click Stream, DataWareHouse) database, Hive database, Doris database, and relational database.

[0037] The query system provided in this invention retrieves metadata by calling a metadata interface service through the platform front-end layer. Based on the query information input by the user terminal, the metadata is assembled to generate query condition data corresponding to the query information. An indicator parsing unit determines the target storage medium for the query result data corresponding to the query condition data based on a pre-established storage mapping relationship between the storage medium and platform data. Based on the target instruction requirements of the target storage medium and the query condition data, a query instruction is generated, enabling the data storage layer to retrieve the query result data from the target storage medium based on the query instruction, thus completing the data query process. This eliminates the need for the user to know the underlying data storage medium in advance or to manually write query instructions, thereby improving query efficiency and accuracy and enhancing the user experience.

[0038] Example 2

[0039] This embodiment is an optimization based on the above-described technical solutions. The explanations of terms that are the same as or corresponding to those in the above embodiments will not be repeated here.

[0040] Figure 3 A structural diagram of another query system provided in an embodiment of the present invention; as shown below. Figure 3As shown, the query system in this embodiment of the invention further includes a query engine layer 13 that is communicatively connected to the data storage layer 12 and the indicator management layer 11, respectively. The query engine layer 13 is used to obtain the query instructions sent by the indicator management layer 11, and determine the target query engine for the query condition data based on the pre-established mapping relationship between platform data and query engines, and transmit the query instructions to the data storage layer through the target query engine.

[0041] In this embodiment, the mapping relationship between platform data and the query engine can be a direct mapping relationship between stored data and the query engine, or it can be a mapping relationship determined by the mapping relationship between the storage medium where the platform data resides and the query engine. For example, the mapping relationship between platform data and the query engine is determined based on a pre-established mapping relationship between the storage medium and the query engine, and a storage mapping relationship between platform data and the storage medium. Through this mapping relationship, the target query engine for the query condition data is determined, and the data query operation is performed using the target query engine.

[0042] The query engines in the query engine layer include at least one of the following: Spark query engine, Prosto query engine, Impala query engine, and JDBC query engine.

[0043] Based on any optional technical solution in this embodiment of the invention, the indicator management layer 11 may optionally include an indicator encapsulation unit 120, used to encapsulate the query condition data according to a preset platform format, so that the indicator parsing unit 110 can generate a query instruction based on the encapsulated query condition data and target instruction requirements. The preset platform format may be an object spectrum format, whose constituent elements include at least one of the following: business, condition, database, table, and relationships between tables. For example, through the query condition data in the object spectrum format, the query business can be determined to be a film and television business, and the query condition is "consumption status of members with valid memberships and an expiration time greater than 30 days," involving tables including a member status table and a member payment table.

[0044] Specifically, the platform front-end layer 10 can send the query condition data to the indicator encapsulation unit 120 in the indicator management layer 11 via a message queue. The indicator encapsulation unit 120 encapsulates the query condition data into an object simplified format and sends the encapsulated query condition data to the indicator parsing unit 110. The indicator parsing unit 110 determines the target storage medium and generates a query instruction based on the target instruction requirements of the target storage medium and the encapsulated query condition data.

[0045] Based on any optional technical solution in the embodiments of the present invention, optionally, the indicator management layer 11 further includes: an indicator cache unit 130, which is communicatively connected to the platform front-end layer 10 and the indicator parsing unit 110 respectively, and is used to receive the query condition data sent by the platform front-end layer 10, perform data storage operation on the query condition data, and send the query condition data to the indicator parsing unit 110.

[0046] In practice, query condition data for each query can be stored, eliminating the need to re-determine query conditions when receiving the same query information, thus improving the convenience and efficiency of the query process. Furthermore, when storing query condition data, it can be stored for a preset storage duration. Specifically, the stored query condition data can be monitored, and when the preset storage duration is reached, the query condition data can be deleted to save storage space.

[0047] Based on any optional technical solution in the embodiments of the present invention, optionally, the data storage layer 12 is also used to call the data monitoring and display service to display the query result data on the interface; and / or, the indicator parsing unit 110 is also used to call the data monitoring and display service to display the media information of the target storage medium and the query condition data on the interface.

[0048] Among them, the data monitoring and display service can be used to monitor the storage information of metadata, the call status of metadata interfaces, the status of platform front-end pages and indicator management, and display the page status based on the monitoring results.

[0049] In this embodiment, to facilitate user viewing of query results, the query result data can be displayed on the interface by calling a data monitoring and display service. Furthermore, to facilitate user viewing of the storage status of the query result data, the media information of the target storage medium and the number of query conditions can be displayed on the interface. For example, the media information includes information such as the name and identifier of the target storage medium. The interface display method can be at least one of table display, graphical display, and text display.

[0050] Based on any optional technical solution in the embodiments of the present invention, optionally, the data storage layer 12 is further configured to, when receiving platform data to be stored, determine the storage medium for the platform data to be stored, call the metadata model storage service, and store the platform data to be stored in the storage medium in the form of a target data table.

[0051] Specifically, when the data storage layer 12 receives platform data to be stored, it can determine whether it has received specified information for a specified storage medium. If so, it determines the storage medium for the platform data to be stored based on the specified information; otherwise, it determines the storage medium based on the current data storage volume of each storage medium. For example, the storage medium with the lowest current data storage volume can be determined as the storage medium.

[0052] The metadata model storage service specifically serves to store data from the data storage layer. In practice, it can be invoked to store platform data to the storage medium. The target data table includes at least one of the following: storage medium address, database name, database description, table name, table description, field name, and field description.

[0053] Furthermore, after storage is completed, the correspondence between the platform data to be stored and the storage medium can be recorded. Based on the correspondence between the platform data and the storage medium, a storage mapping relationship between the platform data and the storage medium can be established. This makes it easier to determine the target storage medium corresponding to the query condition data based on the storage mapping relationship during subsequent data querying, which helps to improve query efficiency and accuracy and save query time.

[0054] Based on any optional technical solution in this embodiment of the invention, optionally, the data storage layer 12 is further used to update the storage mapping relationship based on the correspondence between the platform data to be stored and the storage medium. Specifically, after data storage is completed, it can be determined whether the platform data is newly added platform data. If so, it means that the established storage mapping relationship does not include the correspondence between the platform data to be stored and the storage medium, and the correspondence can be added to the established storage mapping relationship. If the platform data is not newly added platform data, but modified platform data, then only the platform data information corresponding to the storage medium can be modified to the current platform data information to be stored in the storage mapping relationship.

[0055] In this embodiment of the invention, the query condition data is encapsulated to facilitate data transmission; and the obtained query result data is displayed on the interface to facilitate user viewing of the query results, thereby improving the user experience.

[0056] It is worth noting that in the above-described embodiments of the query system, the various units and modules are divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0057] Example 3

[0058] Figure 4 This is a schematic diagram of the overall architecture of a query system provided in an embodiment of the present invention. Figure 4 As shown, the overall architecture of the query system includes data monitoring and display services, metadata interface services, metadata model storage services, OLAP platform front-end layer, OLAP metric management layer, OLAP query engine layer, and OLAP data storage layer. The functions of each service are as follows:

[0059] (1) Metadata storage service can store the metadata and metadata storage table information stored in the data storage layer, which is convenient for the data model interface and the platform front-end layer to use.

[0060] (2) The metadata interface service is a service for querying and retrieving data from metadata. Users can access data from the metadata through the metadata interface service according to different query business needs.

[0061] (3) The data monitoring and display service can be used to monitor the storage information of metadata, the status of metadata interface calls, the status of platform front-end pages and indicator management, and display the page status based on the monitoring results.

[0062] In this embodiment, the roles of the OLAP platform front-end layer, OLAP metric management layer, OLAP query engine layer, and OLAP data storage layer are as follows:

[0063] (1) The front-end layer of the OLAP platform can obtain metadata through the metadata interface service, and assemble the tables and fields of the metadata in the front-end using the received query information to obtain query condition data.

[0064] (2) The OLAP indicator management layer can be used for indicator transmission, indicator encapsulation, indicator parsing, indicator query routing, and indicator data caching. The specific steps include: after the platform front-end layer generates query condition data, it outputs the query condition data to the indicator management layer through a message queue. The indicator management layer encapsulates the query condition data into a unified object spectrum format. The constituent elements of the object spectrum format include at least one of the following: business, condition, database, table, and the relationship between tables. Further, the indicator management layer parses the query condition data, determines the target storage medium corresponding to the query condition data based on the pre-established storage mapping relationship between platform data and storage medium, generates a query instruction based on the query syntax requirements of the target storage medium, sends the query instruction to the corresponding target storage medium in the OLAP data storage layer through the instruction query routing, and caches the query result data.

[0065] (3) The query engines in the OLAP query engine layer include at least one of the following: Spark query engine, Prosto query engine, Impala query engine, and JDBC query engine. The OLAP query engine layer determines the appropriate query engine for processing the data based on the query conditions, and then performs the query operation using the corresponding engine. It should be noted that different query engines can be used to query data stored on different media.

[0066] (4) OLAP data storage layer, used to store platform data. The storage media in the data storage layer include at least one of the following: Druid database connection pool, Clinkhouse (Click Stream, Data WareHouse) database, HIVE database, Doris database, and relational database. Platform data can be stored in the form of data tables. Taking the membership status data in the film and television playback industry as an example, the membership status table obtained after storage is shown in Table 1:

[0067] Table 1

[0068]

[0069] This invention employs a unified index management layer to encapsulate, parse, and route all queries, eliminating the need for users to know the underlying data storage medium and format. It allows data to be stored in different databases, fully leveraging the advantages of each and improving data storage and query speed.

[0070] Example 4

[0071] Figure 5 This is a flowchart illustrating a query method provided in an embodiment of the present invention. The method is applied to a query system, which includes a platform front-end layer, a data storage layer, and an indicator management layer communicatively connected to both the platform front-end layer and the data storage layer; wherein the indicator management layer includes an indicator parsing unit; such as... Figure 5 As shown, the method may specifically include:

[0072] S110. Obtain metadata by calling the metadata interface service through the platform front-end layer, assemble the metadata based on the query information input by the user terminal, generate query condition data corresponding to the query information, and send the query condition data to the indicator parsing unit.

[0073] S120. Based on the pre-established storage mapping relationship between the storage medium and the platform data, the indicator analysis unit determines the target storage medium for the query result data corresponding to the query condition data. Based on the target instruction requirements of the target storage medium and the query condition data, a query instruction is generated and sent to the data storage layer.

[0074] S130. Based on the received query command, the data storage layer retrieves the query result data from the target storage medium and feeds the query result data back to the user terminal.

[0075] Based on any optional technical solution in the embodiments of the present invention, the indicator management layer may optionally include: an indicator encapsulation unit, which encapsulates the query condition data according to a preset platform format so that the indicator parsing unit can generate a query instruction based on the encapsulated query condition data and the target instruction requirements.

[0076] Based on any optional technical solution in the embodiments of the present invention, optionally, the preset platform format is an object simplified spectrum format. The constituent elements of the object simplified spectrum format include at least one of the following elements: business, conditions, library, table, and the relationship between tables.

[0077] Based on any optional technical solution in the embodiments of the present invention, the query system may optionally further include: a query engine layer that is communicatively connected to the data storage layer and the indicator management layer respectively, and the query method may further include:

[0078] The query engine layer obtains the query instructions sent by the indicator management layer, and determines the target query engine for the query condition data based on the pre-established mapping relationship between platform data and query engines. The query instructions are then transmitted to the data storage layer through the target query engine.

[0079] Based on any optional technical solution in the embodiments of the present invention, optionally, the indicator management layer further includes: an indicator caching unit, which is communicatively connected to the platform front-end layer and the indicator parsing unit respectively; the method includes:

[0080] The indicator caching unit receives the query condition data sent by the front-end layer of the receiving platform, performs data storage operations on the query condition data, and sends the query condition data to the indicator parsing unit.

[0081] Based on any optional technical solution in the embodiments of the present invention, the method optionally includes:

[0082] The query results are displayed on the interface by calling the data monitoring and display service through the data storage layer; and / or,

[0083] The indicator analysis unit calls the data monitoring and display service to display the media information of the target storage medium and the query condition data on the interface.

[0084] Based on any optional technical solution in the embodiments of the present invention, the method may optionally include:

[0085] When the data storage layer receives platform data to be stored, it determines the storage medium for the platform data, calls the metadata model storage service, and stores the platform data to be stored in the storage medium in the form of a target data table.

[0086] Based on any optional technical solution in the embodiments of the present invention, the method may optionally include:

[0087] The storage mapping relationship is updated by the data storage layer based on the correspondence between the platform data to be stored and the storage medium.

[0088] Based on any optional technical solution in the embodiments of the present invention, the target data table may optionally include at least one of the following: storage medium address, library name, library description, table name, table description, field name, and field description.

[0089] The query method provided in this embodiment of the invention obtains metadata by calling a metadata interface service through the platform front-end layer, assembles the metadata based on the query information input by the user terminal, generates query condition data corresponding to the query information, and determines the target storage medium for the query result data corresponding to the query condition data through an indicator parsing unit based on a pre-established storage mapping relationship between the storage medium and the platform data. Based on the target instruction requirements of the target storage medium and the query condition data, a query instruction is generated, enabling the data storage layer to obtain the query result data from the target storage medium based on the query instruction, thus completing the data query process. This eliminates the need for the user to know the storage medium of the underlying data in advance and to manually write query instructions, thereby improving query efficiency and accuracy and enhancing the user experience.

[0090] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A query system, characterized in that, include: The system comprises a platform front-end layer, a data storage layer, and an indicator management layer that is communicatively connected to the platform front-end layer and the data storage layer, respectively; wherein the indicator management layer includes an indicator parsing unit. The platform front-end layer is used to call the metadata interface service to obtain metadata, assemble the metadata based on the query information input by the user terminal, generate query condition data corresponding to the query information, and send the query condition data to the indicator parsing unit. The indicator parsing unit is used to determine the target storage medium for the query result data corresponding to the query condition data based on the pre-established storage mapping relationship between the storage medium and the platform data, generate a query instruction based on the target instruction requirements of the target storage medium and the query condition data, and send the query instruction to the data storage layer, wherein the target instruction requirements are the query syntax requirements corresponding to the target storage medium; The data storage layer is used to obtain the query result data from the target storage medium based on the received query instruction, and to feed the query result data back to the user terminal.

2. The system according to claim 1, characterized in that, The management layer for these metrics also includes: The indicator encapsulation unit is used to encapsulate the query condition data according to a preset platform format, so that the indicator parsing unit can generate the query instruction based on the encapsulated query condition data and the target instruction requirements.

3. The system according to claim 2, characterized in that, The preset platform format is an object simplified spectrum format, and the constituent elements of the object simplified spectrum format include at least one of the following elements: business, conditions, library, table, and the relationship between tables.

4. The system according to claim 1, characterized in that, Also includes: The query engine layer is communicatively connected to both the data storage layer and the indicator management layer, wherein... The query engine layer is used to obtain the query instruction sent by the indicator management layer, and based on the pre-established mapping relationship between platform data and query engines, determine the target query engine for the query condition data, and transmit the query instruction to the data storage layer through the target query engine.

5. The system according to claim 1, characterized in that, The management layer for these metrics also includes: The indicator caching unit is communicatively connected to both the platform front-end layer and the indicator parsing unit. It is used to receive the query condition data sent by the platform front-end layer, perform data storage operations on the query condition data, and send the query condition data to the indicator parsing unit.

6. The system according to claim 1, characterized in that, The data storage layer is also used to call the data monitoring and display service to display the query results data on the interface; and / or, The indicator parsing unit is also used to call the data monitoring and display service to display the media information and query condition data of the target storage medium on the interface.

7. The system according to claim 1, characterized in that, The data storage layer is also used to, when receiving platform data to be stored, determine the storage medium for the platform data to be stored, call the metadata model storage service, and store the platform data to be stored in the storage medium in the form of a target data table.

8. The system according to claim 7, characterized in that, The data storage layer is also used to update the storage mapping relationship based on the correspondence between the platform data to be stored and the storage medium.

9. The system according to claim 7, characterized in that, The target data table includes at least one of the following: storage medium address, library name, library description, table name, table description, field name, and field description.

10. A query method, characterized in that, The method is applied to a query system, which includes a platform front-end layer, a data storage layer, and an indicator management layer that is communicatively connected to both the platform front-end layer and the data storage layer; wherein the indicator management layer includes an indicator parsing unit; the method includes: The platform front-end layer calls the metadata interface service to obtain metadata, assembles the metadata based on the query information input by the user terminal, generates query condition data corresponding to the query information, and sends the query condition data to the indicator parsing unit. The indicator parsing unit determines the target storage medium for the query result data corresponding to the query condition data based on the pre-established storage mapping relationship between the storage medium and the platform data. Based on the target instruction requirements of the target storage medium and the query condition data, a query instruction is generated and sent to the data storage layer. The target instruction requirements are the query syntax requirements corresponding to the target storage medium. The data storage layer retrieves the query result data from the target storage medium based on the received query instruction, and then feeds the query result data back to the user terminal.

Images