Metadata management device and method

Abstract

The present invention discloses a metadata management device and method, which belongs to the field of metadata management technology. The technical problem to be solved is how to realize the management of metadata on the edge side and the end side of the cloud-edge-end system. It includes a user-end module, an execution module configured in the database, a synchronization module and a metadata thread configured in the client. The user-end module is used to issue metadata operation commands and metadata query commands; the execution module is used to: perform write operations on the database system table and submit transactions, and call the synchronization module to send metadata information corresponding to the metadata operation command to the metadata operation thread; the metadata operation thread is used to perform metadata operations on the local client. The metadata thread is used to: return the queried metadata to the user-end module, and if no metadata is found, send a metadata query request to the synchronization module; the synchronization module is used to query metadata from the database system table, and call the metadata thread to return the queried metadata to the user-end module.

Description

Technical Field

[0001] The present invention relates to the field of metadata management technology, and in particular to a metadata management device and method. Background Art

[0002] The digital energy platform is a cloud-edge-end system centered around a database. Databases are deployed on both the cloud and edge sides, providing data storage and computing capabilities. The edge-side collection layer configures and collects microgrid device operating status data. This collected microgrid data is then uploaded to the edge-side database for storage and computing. Furthermore, data is periodically uploaded from the edge side to the cloud, leveraging the database's powerful computing capabilities for data learning, analysis, and modeling.

[0003] The metadata management unit is responsible for the preservation and management of the metadata of the entire digital energy platform, and manages various definitions and configuration information such as the microgrid portal, tenants, access devices, sampling points, and users. At the same time, the metadata will be synchronized between the cloud and the edge according to the corresponding policies and needs. Specifically, users can configure the microgrid portal and tenant information in the cloud, and metadata information such as sampling devices and sampling points under the tenant on the edge. The metadata information stored by devices at different locations on the cloud and the edge is different. Since the end side does not contain any storage unit, the metadata will disappear after the device is restarted; and the edge side metadata is saved in the database system and can be retrieved after the device is restarted.

[0004] Based on the digital energy platform's demand for metadata, how to implement metadata management on the edge and end sides of the cloud-edge-end system, ensure that the energy management platform can more effectively and quickly operate and query metadata in scenarios with multiple users, multiple tenants, multiple devices, and multiple collection points, and ensure the stable operation of the digital energy system, is a technical problem that needs to be solved. Summary of the Invention

[0005] The technical task of the present invention is to address the above shortcomings and provide a metadata management device and method to solve the technical problem of how to realize the management of metadata on the edge and end sides of the cloud-edge system, and ensure that the energy management platform can perform metadata operations and queries more effectively and quickly in scenarios with multiple users, multiple tenants, multiple devices, and multiple collection points.

[0006] In a first aspect, a metadata management device of the present invention is characterized in that it is used to manage metadata for an energy digital platform of a client and a database, wherein a metadata function module for managing metadata is configured on the client, and the client is configured on each node device at the edge;

[0007] The management device includes a user-side module, an execution module configured in a database, a synchronization module and a metadata thread configured in a client;

[0008] The user-side module is used to issue metadata operation commands and metadata query commands created by users, wherein the metadata operation commands include metadata creation commands, metadata update commands, and metadata deletion commands;

[0009] For the metadata operation command, the execution module is used to: perform a write operation on the database system table and commit the transaction based on the metadata operation command received from the user-side module, and call the synchronization module to send metadata information corresponding to the metadata operation command to the metadata operation thread; the metadata operation thread is used to perform metadata operations on the local client based on the metadata information;

[0010] For the metadata query command, the metadata thread is used to execute: performing a metadata query based on the metadata query command received from the user-side module, returning the queried metadata to the user-side module; if no metadata is found, sending a metadata query request to the synchronization module; the synchronization module is used to query metadata from the database system table based on the metadata query request, and calling the metadata thread to save the queried metadata to the metadata function module and return it to the user-side module.

[0011] Preferably, the metadata creation command is an SQL statement, and the corresponding metadata information is metadata information of the newly added metadata;

[0012] For the metadata creation command, the execution module is used to execute: creating a transaction based on the metadata creation command, performing verification and business logic processing on the created metadata, and writing metadata information of the newly added metadata into the database system table; after committing the transaction, calling the synchronization interface to send the metadata information of the newly added metadata to the metadata thread;

[0013] The metadata thread is used to call the new interface of the metadata function module to save metadata information of the newly added metadata to the local client.

[0014] Preferably, the metadata update command is an SQL statement, and the corresponding metadata information is metadata information for updating metadata;

[0015] For the metadata update command, the execution module is used to execute: based on the metadata update command, calling the synchronization module to send an invalid message to the metadata thread;

[0016] The metadata thread is used to call the invalid interface of the metadata function module to set the corresponding metadata to an invalid state;

[0017] The execution module is used to execute: writing the updated metadata into the database system table, and calling the synchronization module to send the metadata information of the updated metadata to the metadata thread;

[0018] The metadata thread is used to call the update interface of the metadata function module to update the corresponding metadata information on the local client.

[0019] Preferably, the metadata deletion command is an SQL statement, and the corresponding metadata information is metadata information for deleting metadata;

[0020] For the metadata deletion command, the execution module is used to execute: deleting the corresponding metadata from the database system table based on the metadata deletion command, and calling the synchronization module to send metadata information of the deleted metadata to the metadata thread;

[0021] The metadata thread is used to call the deletion interface of the metadata function module to delete the corresponding metadata from the local client.

[0022] Preferably, the metadata query command is an SQL statement;

[0023] For the metadata query command, the metadata thread is used to execute: calling the query interface of the metadata function module to query the corresponding metadata; if the metadata exists and is valid, returning the metadata to the user-end module; if the metadata does not exist or is invalid, calling the request interface of the metadata thread through the metadata function module to query the corresponding metadata;

[0024] The metadata thread calls the synchronization module through the request interface, and the synchronization module is used to query the corresponding metadata from the database system table and return the queried metadata to the metadata thread;

[0025] The metadata thread is used to return the returned metadata to the user end module through the metadata function module.

[0026] In a second aspect, the present invention provides a metadata management method, which manages metadata for an energy digital platform including a client and a database based on the metadata management device according to any one of the first aspects, the method comprising the following steps:

[0027] Sending metadata operation commands and metadata query commands created by the user through the user-side module, wherein the metadata operation commands include metadata creation commands, metadata update commands, and metadata deletion commands;

[0028] For the metadata operation command, based on the metadata operation command received from the user-side module, the execution module performs a write operation on the database system table and commits the transaction, and calls the synchronization module to send metadata information corresponding to the metadata operation command to the metadata operation thread; based on the metadata information, the metadata operation is performed on the local client through the metadata thread;

[0029] For the metadata query command, based on the metadata query command received from the user-side module, the metadata query is executed through the metadata thread, and the queried metadata is returned to the user-side module. If no metadata is found, a metadata query request is sent to the synchronization module; based on the metadata query request, metadata is queried from the database system table through the synchronization module, and the metadata thread is called to save the queried metadata to the metadata function module and return it to the user-side module.

[0030] Preferably, the metadata creation command is an SQL statement, and the corresponding metadata information is metadata information of the newly added metadata;

[0031] For the metadata creation command, execute as follows:

[0032] Create a command based on the metadata and create a transaction by executing the module;

[0033] The created metadata is verified and business logic processed through the execution module, and the metadata information of the newly added metadata is written into the database system table;

[0034] After the transaction is committed through the execution module, the synchronization interface is called to send the metadata information of the newly added metadata to the metadata thread;

[0035] The metadata thread calls the new interface of the metadata function module to save the metadata information of the newly added metadata to the local client.

[0036] Preferably, the metadata update command is an SQL statement, and the corresponding metadata information is metadata information for updating metadata;

[0037] For the metadata update command, execute as follows:

[0038] Based on the metadata update command, the execution module calls the synchronization module to send an invalid message to the metadata thread;

[0039] Set the corresponding metadata to an invalid state through the metadata thread;

[0040] Write the updated metadata into the database system table and call the synchronization module to send the metadata information of the updated metadata to the metadata thread;

[0041] The metadata thread calls the update interface of the metadata function module to update the corresponding metadata information on the local client.

[0042] Preferably, the metadata deletion command is an SQL statement, and the corresponding metadata information is metadata information for deleting metadata;

[0043] For the metadata deletion command, execute as follows:

[0044] Based on the metadata deletion command, the corresponding metadata is deleted from the database system table through the execution module, and the synchronization module is called to send metadata information of the deleted metadata to the metadata thread;

[0045] The metadata thread calls the deletion interface of the metadata function module to delete the corresponding metadata from the local client.

[0046] Preferably, the metadata query command is an SQL statement;

[0047] For the metadata query command, execute as follows:

[0048] Call the query interface of the metadata function module through the metadata thread to query the corresponding metadata;

[0049] If the metadata exists and is valid, returning the metadata to the user-side module;

[0050] If the metadata does not exist or is in an invalid state, the metadata function module calls the request interface of the metadata thread to query the corresponding metadata;

[0051] The synchronization module is called through the request interface of the metadata thread, and the corresponding metadata is retrieved from the database system table through the synchronization module and returned to the metadata thread;

[0052] The metadata thread returns the returned metadata to the user-side module through the metadata function module.

[0053] The metadata management device and method of the present invention have the following advantages:

[0054] 1. It can effectively ensure that metadata information of the energy management system is correctly and timely stored and managed;

[0055] 2. When users need to query metadata information, they can obtain the correct metadata information, which is consistent with the metadata of the database system table, ensuring the stable operation of the energy management system;

[0056] 3. At the same time, since the metadata function module runs independently on the Agent of each node device on the edge, metadata synchronization between the edge and the end can be achieved through the interaction of the synchronization module sync_module and the metadata thread. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0058] The present invention will be further described below with reference to the accompanying drawings.

[0059] Figure 1 This is a flowchart of a workflow for metadata creation by a metadata management device according to Example 1;

[0060] Figure 2 This is a flowchart of a metadata management apparatus for updating metadata in accordance with Example 1;

[0061] Figure 3 This is a flowchart of a metadata management device for metadata deletion in Example 1;

[0062] Figure 4 This is a flowchart of the workflow of a metadata management device for metadata query in Example 1. DETAILED DESCRIPTION

[0063] The present invention will be further described below with reference to the accompanying drawings and specific embodiments so that those skilled in the art can better understand the present invention and implement it. However, the embodiments given are not intended to limit the present invention. Unless there is a conflict, the embodiments of the present invention and the technical features in the embodiments may be combined with each other.

[0064] Embodiments of the present invention provide a metadata management device and method for solving the technical problem of how to manage metadata on the edge side and the end side of a cloud-edge-end system.

[0065] Example 1:

[0066] The present invention provides a metadata management device, including a user-end module, an execution module configured in a database, a synchronization module and a metadata thread configured in a client, for performing metadata management on an energy digital platform of the client and the database. The client is configured with a metadata function module for managing metadata, and each node device at the edge is configured with the client.

[0067] The user-side module is used to issue metadata operation commands and metadata query commands created by users. The metadata operation commands include metadata creation commands, metadata update commands, and metadata deletion commands.

[0068] For the metadata operation command, the execution module is used to execute: based on the metadata operation command received from the user-end module, write the database system table and commit the transaction, and call the synchronization module to send the metadata information corresponding to the metadata operation command to the metadata operation thread; the metadata operation thread is used to perform metadata operations on the local client based on the metadata information.

[0069] The metadata creation command is an SQL statement, and the corresponding metadata information is the metadata information of the newly added metadata.

[0070] like Figure 1 As shown, for the metadata creation command, the execution module is used to execute: create a transaction based on the metadata creation command, verify and process the created metadata, and write the metadata information of the newly added metadata into the database system table. After committing the transaction, call the synchronization interface to send the metadata information of the newly added metadata to the metadata thread.

[0071] Correspondingly, the metadata thread is used to call the new interface of the metadata function module to save the metadata information of the newly added metadata to the local client.

[0072] The metadata update command is an SQL statement, and the corresponding metadata information is metadata information of updated metadata.

[0073] For the metadata update command, the execution module is used to execute: based on the metadata update command, calling the synchronization module to send an invalid message to the metadata thread.

[0074] Correspondingly, the metadata thread is used to call the invalid interface of the metadata function module to set the corresponding metadata to an invalid state.

[0075] Correspondingly, the execution module is used to execute: writing the updated metadata into the database system table, and calling the synchronization module to send the metadata information of the updated metadata to the metadata thread.

[0076] Correspondingly, the metadata thread is used to call the update interface of the metadata function module to update the corresponding metadata information on the local client.

[0077] The metadata deletion command is an SQL statement, and the corresponding metadata information is metadata information for deleting metadata.

[0078] like Figure 3As shown, for the metadata deletion command, the execution module is configured to: delete the corresponding metadata from the database system table based on the metadata deletion command, and call the synchronization module to send metadata deletion information to the metadata thread. The metadata thread is configured to call the deletion interface of the metadata function module to delete the corresponding metadata from the local client.

[0079] For the metadata query command, the metadata thread is used to execute: performing a metadata query based on the metadata query command received from the user-side module, returning the queried metadata to the user-side module; if no metadata is found, sending a metadata query request to the synchronization module; the synchronization module is used to query metadata from the database system table based on the metadata query request, and calling the metadata thread to save the queried metadata to the metadata function module and return it to the user-side module.

[0080] As a specific implementation, the metadata query command is an SQL statement.

[0081] like Figure 4 As shown, for the metadata query command, the metadata thread is used to execute: calling the query interface of the metadata function module to query the corresponding metadata, and if the metadata exists and is valid, returning the metadata to the user-end module; if the metadata does not exist or the metadata is invalid, calling the request interface of the metadata thread through the metadata function module to query the corresponding metadata.

[0082] Correspondingly, the metadata thread calls the synchronization module through the request interface, and the synchronization module is used to query the corresponding metadata from the database system table and return the queried metadata to the metadata thread;

[0083] Correspondingly, the metadata thread is used to return the returned metadata to the user-end module through the metadata function module.

[0084] The device of this embodiment can realize the addition, update, deletion and query of metadata. The specific workflow is as follows:

[0085] Step 1: User creates metadata information:

[0086] Step 1.1: The user creates metadata configuration.

[0087] Step 1.2: The metadata information is processed in the execution module of the Inspur Yunxi database and the metadata is written into the system table.

[0088] Step 1.3: The execution module sends the newly added metadata to the metadata synchronization module sync_module; the sync_module sends the newly added metadata information to the metadata thread on the Agent side.

[0089] Step 1.4: The metadata thread calls the newly added interface of the metadata function module to save the metadata information.

[0090] Step 2: User updates metadata information

[0091] Step 2.1: User sends configuration for updating metadata

[0092] Step 2.2: The execution module of Inspur Yunxi Database notifies the sync_module to set the corresponding metadata information to invalid. The sync_module sends an invalid message to the metadata thread on the Agent side. Step 2.3: The metadata thread calls the invalid interface of the metadata function module to invalidate the metadata.

[0093] Step 2.4: The execution module writes the updated metadata to the system table.

[0094] Step 2.5: The execution module sends the updated metadata information to the sync_module; the sync_module sends the updated metadata information to the metadata thread.

[0095] Step 2.6: The metadata thread calls the update interface of the metadata function module to update the metadata information.

[0096] Step 3: User deletes metadata information:

[0097] Step 3.1: The user sends a request to delete metadata.

[0098] Step 3.2: The execution module deletes the metadata information from the system table.

[0099] Step 3.3: The execution module sends the metadata deletion information to the sync_module; the sync_module sends the metadata deletion information to the metadata thread.

[0100] Step 3.4: The metadata thread calls the deletion interface of the metadata function module to delete the metadata.

[0101] Step 4: User queries metadata information:

[0102] Step 4.1: The user calls the query interface of the metadata function module to query metadata information.

[0103] Step 4.2: If the metadata exists and is valid, return the metadata to the user.

[0104] Step 4.3: If the metadata information does not exist or is invalid, the metadata function module calls the request interface of the metadata thread to query the metadata.

[0105] Step 4.4: The metadata thread calls the sync_module interface to query metadata information from the database system table and returns it to the metadata thread.

[0106] Step 4.5: The metadata function module receives the query result of the metadata thread and returns the query result to the user.

[0107] Example 2:

[0108] The present invention provides a metadata management method, which manages metadata for an energy digital platform including a client and a database based on the metadata management device disclosed in Example 1. The method includes the following steps:

[0109] S100: Sending metadata operation commands and metadata query commands created by the user through the user-side module. The metadata operation commands include metadata creation commands, metadata update commands, and metadata deletion commands.

[0110] S200. For the metadata operation command, based on the metadata operation command received from the user-side module, the execution module performs a write operation on the database system table and commits the transaction, and calls the synchronization module to send the metadata information corresponding to the metadata operation command to the metadata operation thread; based on the metadata information, the metadata operation is performed on the local client through the metadata thread.

[0111] The metadata creation command is an SQL statement, and the corresponding metadata information is metadata information of newly added metadata.

[0112] For the metadata creation command, execute as follows:

[0113] (1) creating a command based on the metadata and creating a transaction by executing a module;

[0114] (2) Verify and process the created metadata through the execution module, and write the metadata information of the newly added metadata into the database system table;

[0115] (3) After the transaction is committed through the execution module, the synchronization interface is called to send the metadata information of the newly added metadata to the metadata thread;

[0116] (4) Call the new interface of the metadata function module through the metadata thread and save the metadata information of the newly added metadata to the local client.

[0117] The metadata update command is an SQL statement, and the corresponding metadata information is the metadata information of the updated metadata.

[0118] For the metadata update command, execute as follows:

[0119] (1) Based on the metadata update command, the execution module calls the synchronization module to send an invalid message to the metadata thread;

[0120] (2) Setting the corresponding metadata to an invalid state through the metadata thread;

[0121] (3) Write the updated metadata into the database system table and call the synchronization module to send the metadata information of the updated metadata to the metadata thread;

[0122] (4) Call the update interface of the metadata function module through the metadata thread to update the corresponding metadata information on the local client.

[0123] The metadata deletion command is an SQL statement, and the corresponding metadata information is metadata information for deleting metadata.

[0124] For the metadata deletion command, execute as follows:

[0125] (1) Based on the metadata deletion command, the corresponding metadata is deleted from the database system table through the execution module, and the synchronization module is called to send metadata information of the deleted metadata to the metadata thread;

[0126] (2) Call the deletion interface of the metadata function module through the metadata thread to delete the corresponding metadata from the local client.

[0127] S300: For the metadata query command, based on the metadata query command received from the user-side module, execute the metadata query through the metadata thread, return the queried metadata to the user-side module, and if no metadata is found, send a metadata query request to the synchronization module; based on the metadata query request, query metadata from the database system table through the synchronization module, and call the metadata thread to return the queried metadata to the user-side module.

[0128] The metadata query command is an SQL statement. For the metadata query command, execute as follows:

[0129] (1) Call the query interface of the metadata function module through the metadata thread to query the corresponding metadata;

[0130] (2) If the metadata exists and is valid, return the metadata to the user-side module;

[0131] (3) If the metadata does not exist or is in an invalid state, the metadata function module calls the request interface of the metadata thread to query the corresponding metadata;

[0132] (4) calling the synchronization module through the request interface of the metadata thread, querying the corresponding metadata from the database system table through the synchronization module and returning the queried metadata to the metadata thread;

[0133] (5) Based on the metadata thread, the returned metadata is returned to the user-end module through the metadata function module.

[0134] The present invention has been shown and described in detail above through the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Based on the above multiple embodiments, those skilled in the art can know that the means in the above different embodiments can be combined to obtain more embodiments of the present invention, and these embodiments are also within the scope of protection of the present invention.

Claims

1. A metadata management device, characterized in that: The energy digital platform is used to manage metadata for the client and database. The client is equipped with a metadata function module for managing metadata, and each node device at the edge is equipped with the client; The management device includes a user-side module, an execution module configured in a database, a synchronization module and a metadata thread configured in a client; The user-side module is used to issue metadata operation commands and metadata query commands created by users, wherein the metadata operation commands include metadata creation commands, metadata update commands, and metadata deletion commands; For the metadata operation command, the execution module is used to execute: based on the metadata operation command received from the user-side module, perform a write operation on the database system table and commit the transaction, and call the synchronization module to send metadata information corresponding to the metadata operation command to the metadata operation thread; The metadata operation thread is used to perform metadata operations on the local client based on metadata information; For the metadata query command, the metadata thread is used to execute: performing a metadata query based on the metadata query command received from the user-side module, returning the queried metadata to the user-side module, and if no metadata is found, sending a metadata query request to the synchronization module; The synchronization module is used to query metadata from the database system table based on the metadata query request, and call the metadata thread to save the queried metadata to the metadata function module and return it to the user-end module.

2. The metadata management device according to claim 1, wherein: The metadata creation command is an SQL statement, and the corresponding metadata information is the metadata information of the newly added metadata; For the metadata creation command, the execution module is used to execute: creating a transaction based on the metadata creation command, performing verification and business logic processing on the created metadata, and writing metadata information of the newly added metadata into the database system table; after committing the transaction, calling the synchronization interface to send the metadata information of the newly added metadata to the metadata thread; The metadata thread is used to call the new interface of the metadata function module to save metadata information of the newly added metadata to the local client.

3. The metadata management device according to claim 1, wherein: The metadata update command is an SQL statement, and the corresponding metadata information is the metadata information of the updated metadata; For the metadata update command, the execution module is used to execute: based on the metadata update command, calling the synchronization module to send an invalid message to the metadata thread; The metadata thread is used to call the invalid interface of the metadata function module to set the corresponding metadata to an invalid state; The execution module is used to execute: writing the updated metadata into the database system table, and calling the synchronization module to send the metadata information of the updated metadata to the metadata thread; The metadata thread is used to call the update interface of the metadata function module to update the corresponding metadata information on the local client.

4. The metadata management device according to claim 1, wherein: The metadata deletion command is an SQL statement, and the corresponding metadata information is the metadata information for deleting metadata; For the metadata deletion command, the execution module is used to execute: deleting the corresponding metadata from the database system table based on the metadata deletion command, and calling the synchronization module to send metadata information of the deleted metadata to the metadata thread; The metadata thread is used to call the deletion interface of the metadata function module to delete the corresponding metadata from the local client.

5. The metadata management device according to claim 1, wherein: The metadata query command is an SQL statement; For the metadata query command, the metadata thread is used to execute: calling the query interface of the metadata function module to query the corresponding metadata, and if the metadata exists and is valid, returning the metadata to the user end module; If the metadata does not exist or is in an invalid state, the metadata function module calls the request interface of the metadata thread to query the corresponding metadata; The metadata thread calls the synchronization module through the request interface, and the synchronization module is used to query the corresponding metadata from the database system table and return the queried metadata to the metadata thread; The metadata thread is used to save the returned metadata to the metadata function module and return it to the user end module through the metadata function module.

6. A metadata management method, characterized in that: The metadata management device according to any one of claims 1 to 5 is used to manage metadata on an energy digital platform including a client and a database, and the method includes the following steps: Sending metadata operation commands and metadata query commands created by the user through the user-side module, wherein the metadata operation commands include metadata creation commands, metadata update commands, and metadata deletion commands; For the metadata operation command, based on the metadata operation command received from the user-side module, the execution module performs a write operation on the database system table and commits the transaction, and calls the synchronization module to send the metadata information corresponding to the metadata operation command to the metadata operation thread; Based on the metadata information, metadata operations are performed on the local client through the metadata thread; For the metadata query command, based on the metadata query command received from the client module, execute metadata query through the metadata thread, return the queried metadata to the client module, and if no metadata is found, send a metadata query request to the synchronization module; Based on the metadata query request, metadata is queried from the database system table through the synchronization module, and the metadata thread is called to save the queried metadata to the metadata function module and return it to the user end module.

7. The metadata management method according to claim 6, characterized in that: The metadata creation command is an SQL statement, and the corresponding metadata information is the metadata information of the newly added metadata; For the metadata creation command, execute as follows: Create a command based on the metadata and create a transaction by executing the module; The created metadata is verified and business logic processed through the execution module, and the metadata information of the newly added metadata is written into the database system table; After the transaction is committed through the execution module, the synchronization interface is called to send the metadata information of the newly added metadata to the metadata thread; The metadata thread calls the new interface of the metadata function module to save the metadata information of the newly added metadata to the local client.

8. The metadata management method according to claim 6, characterized in that: The metadata update command is an SQL statement, and the corresponding metadata information is the metadata information of the updated metadata; For the metadata update command, execute as follows: Based on the metadata update command, the execution module calls the synchronization module to send an invalid message to the metadata thread; Set the corresponding metadata to an invalid state through the metadata thread; Write the updated metadata into the database system table and call the synchronization module to send the metadata information of the updated metadata to the metadata thread; The metadata thread calls the update interface of the metadata function module to update the corresponding metadata information on the local client.

9. The metadata management method according to claim 6, characterized in that: The metadata deletion command is an SQL statement, and the corresponding metadata information is the metadata information for deleting metadata; For the metadata deletion command, execute as follows: Based on the metadata deletion command, the corresponding metadata is deleted from the database system table through the execution module, and the synchronization module is called to send metadata information of the deleted metadata to the metadata thread; The metadata thread calls the deletion interface of the metadata function module to delete the corresponding metadata from the local client.

10. The metadata management method according to claim 6, characterized in that: The metadata query command is an SQL statement; For the metadata query command, execute as follows: Call the query interface of the metadata function module through the metadata thread to query the corresponding metadata; If the metadata exists and is valid, returning the metadata to the user-side module; If the metadata does not exist or is in an invalid state, the metadata function module calls the request interface of the metadata thread to query the corresponding metadata; The synchronization module is called through the request interface of the metadata thread, and the corresponding metadata is retrieved from the database system table through the synchronization module and returned to the metadata thread; The metadata thread returns the returned metadata to the user-side module through the metadata function module.

Images