CN114816470A - Metabase management method, apparatus, electronic device and medium - Google Patents

Abstract

The application provides a metadata database management method, a metadata database management device, electronic equipment and media, and belongs to the technical field of computers. The method comprises the following steps: in response to a version change operation for at least one of the plurality of metadatabase nodes, determining a target metadatabase version corresponding to the version change operation; determining a target dependency metadata database version and target script information corresponding to the target metadata database version according to the corresponding relation between different metadata database versions and the dependency metadata database version and the script information; when a deployment record of a target dependency metadata database version exists in a target metadata database node, extracting script applicable configuration and a script storage address from target script information; when the applicable configuration of the script is matched with the configuration information of the target metadatabase node, acquiring a script program from a script storage address; and executing the script program, and deploying the target metadata base version at the target metadata base node. And the normal operation of the metadata database version after deployment is ensured.

Description

Metabase management method, apparatus, electronic device and medium

technical field

The present application belongs to the field of computer technology, and in particular relates to a metadata database management method, apparatus, electronic device and medium.

Background technique

With the rapid iteration of software products, there is data sharing and interaction between products and product modules, and there are many requirements for modification of database table structure and metadata, and even each product under iteration has modification requirements for the same database table at the same time. , resulting in mutual restraint between various products, often causing conflicts, and it is difficult to go online. For example, there are still differences in the data table structure and metadata of the same product in different system architectures and individual project environments, which are difficult to handle. Therefore, there is an urgent need for a version management method to do standardized management, resolve these conflicts in R&D, and improve the speed of release and launch.

SUMMARY OF THE INVENTION

Some embodiments of the present application provide a metadata database management method, apparatus, electronic device, and medium, so as to solve the above technical problems as much as possible.

Some embodiments of the present application provide a method for managing a metadata database, which is applied to a metadata database management terminal, where the metadata database management terminal is connected to a plurality of metadata database nodes, and the method includes:

In response to a version change operation for at least one metabase node in the plurality of metabase nodes, determining a target metabase version corresponding to the version change operation;

Determine the target dependent metabase version and target script information corresponding to the target metabase version according to the correspondence between different metabase versions, dependent metabase versions, and script information;

When there is a deployment record of the target-dependent metabase version in the target metabase node, extracting a script applicable configuration and a script storage address from the target script information;

Obtaining a script program from the script storage address when the script applicable configuration matches the configuration information of the target metabase node;

The script program is executed to deploy the target metabase version on the target metabase node.

Optionally, the corresponding relationship between the metadata version and the script information is constructed by the following steps:

In response to the construction instruction of the corresponding relationship, displaying a version tree containing the hierarchical relationship between the metadata database versions;

In response to the newly added operation to any version parent node in the version tree, create a version child node subordinate to the version parent node, and obtain and store the metadata database version information;

Acquire and store script information in response to a script entry operation for the metabase version information;

The metadata database version information and the script information are associated and stored.

Optionally, after displaying the version tree including the association relationship between the metadata database versions, the method further includes:

In response to an editing operation on any target version node in the version tree, displaying version information and script information corresponding to the target version node;

In response to an editing operation on the version information and/or the script information, the version information and/or the script information indicated by the editing operation is updated.

Optionally, the determining the target metadata database version corresponding to the version change operation includes:

When there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, change the intermediate metabase version and the version indicated by the version change operation The metabase version of the target metabase version.

Optionally, using the intermediate metabase version and the metabase version indicated by the version change operation as the target metabase version includes:

When there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, change the intermediate metabase version and the version indicated by the version change operation The metabase version of the to-be-updated metabase version;

Use the metabase version to be updated with the lowest database version level as the target metabase version;

After the executing the script program, after the target metabase node deploys the target metabase version, the method further includes:

Remove the target metabase version from the to-be-updated metabase version, and re-enter the step of using the lowest-level metabase version to be updated as the target metabase version, until the to-be-updated metabase version does not exist , and finish executing the version update process for the target metabase node.

Optionally, after taking the metabase version to be updated with the lowest database version level as the target metabase version, the method further includes:

When the update of the target metabase version fails, the updated content for the target metabase version is rolled back, and the execution of the version update process for the target metabase node is ended.

Optionally, the node information of the metabase node is edited through the following steps:

In response to the editing instruction of the metadata node information, displaying the metadata database node tree including the hierarchical relationship between the metadata database nodes;

In response to an editing operation for any target metabase node identifier in the metabase node tree, displaying the metabase node information corresponding to the target metabase node identifier;

The metabase node information is updated in response to an edit operation on the metabase node information.

Some embodiments of the present application provide a metadata database management device, which is applied to a metadata database management terminal, and the metadata database management terminal is connected to a plurality of metadata database nodes, and the device includes:

an input module, configured to, in response to a version change operation for at least one metabase node in the plurality of metabase nodes, determine a target metabase version corresponding to the version change operation;

a verification module, configured to determine the target-dependent metabase version and target script information corresponding to the target metabase version according to the correspondence between different metabase versions and the dependent metabase version and script information;

When there is a deployment record of the target-dependent metabase version in the target metabase node, extracting a script applicable configuration and a script storage address from the target script information;

Obtaining a script program from the script storage address when the script applicable configuration matches the configuration information of the target metabase node;

A deployment module, configured to execute the script program, and deploy the target metabase version on the target metabase node.

Optionally, the device further includes: an editing module for:

In response to the construction instruction of the corresponding relationship, displaying a version tree containing the hierarchical relationship between the metadata database versions;

In response to the newly added operation to any version parent node in the version tree, create a version child node subordinate to the version parent node, and obtain and store the metadata database version information;

Acquire and store script information in response to a script entry operation for the metabase version information;

The metadata database version information and the script information are associated and stored.

Optionally, the editing module is also used for:

In response to an editing operation on any target version node in the version tree, displaying version information and script information corresponding to the target version node;

In response to an editing operation on the version information and/or the script information, the version information and/or the script information indicated by the editing operation is updated.

Optionally, the verification module is further configured to, when there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, verify the The intermediate metabase version and the metabase version indicated by the version change operation are used as the target metabase version.

Optionally, the verification module is also used for:

When there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, change the intermediate metabase version and the version indicated by the version change operation The metabase version of the to-be-updated metabase version;

Use the metabase version to be updated with the lowest database version level as the target metabase version;

Remove the target metabase version from the to-be-updated metabase version, and re-enter the step of using the lowest-level metabase version to be updated as the target metabase version, until the to-be-updated metabase version does not exist , and finish executing the version update process for the target metabase node.

Optionally, the deployment module is also used for:

When the update of the target metabase version fails, the updated content for the target metabase version is rolled back, and the execution of the version update process for the target metabase node is ended.

Optionally, the editing module is also used for:

In response to the editing instruction of the metadata node information, displaying the metadata database node tree including the hierarchical relationship between the metadata database nodes;

In response to an editing operation for any target metabase node identifier in the metabase node tree, displaying the metabase node information corresponding to the target metabase node identifier;

The metabase node information is updated in response to an edit operation on the metabase node information.

Some embodiments of the present application provide a computing processing device, including:

a memory in which computer readable code is stored;

One or more processors, when the computer readable code is executed by the one or more processors, the computing processing device performs the metadata database management method as described above.

Some embodiments of the present application provide a computer program, including computer-readable code, which, when the computer-readable code is executed on a computing processing device, causes the computing processing device to execute the above-described metadata database management method.

Some embodiments of the present application provide a computer-readable medium, in which the above-mentioned metadata database management method is stored.

A metadata database management method, device, electronic device and medium provided by the present application, by centralizing the metadata version update process to the metadata database management terminal for unified management, so that data is processed at the metadata database node connected to the metadata database management terminal. When updating, first confirm that the metabase node has a dependent metabase version corresponding to the target metabase version to be updated, ensure that the deployed version can be supported by the dependent metabase version, and then confirm the configuration information of the metabase node and the target metabase. After the scripts of the nodes match the applicable configuration, the script program is executed to deploy the target metabase version, which ensures that the metabase version can run normally after deployment, and that if a problem occurs, the version deployment record can be quickly checked on the metadata management end.

The above description is only an overview of the technical solution of the present application. In order to be able to understand the technical means of the present application more clearly, it can be implemented according to the content of the description, and in order to make the above-mentioned and other purposes, features and advantages of the present application more obvious and easy to understand , and the specific embodiments of the present application are listed below.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the accompanying drawings used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1 schematically shows a schematic flowchart of a method for managing a metadata database provided by some embodiments of the present application;

FIG. 2 schematically shows a schematic diagram of the principle of a metadata database management method provided by some embodiments of the present application;

FIG. 3 schematically shows one of the schematic flowcharts of another metadata database management method provided by some embodiments of the present application;

FIG. 4 schematically shows the second schematic flowchart of another metadata database management method provided by some embodiments of the present application;

FIG. 5 schematically shows the third schematic flowchart of another metadata database management method provided by some embodiments of the present application;

FIG. 6 schematically shows a schematic diagram of the principle of another metadata database management method provided by some embodiments of the present application;

FIG. 7 schematically shows the fourth schematic flow chart of another metadata database management method provided by some embodiments of the present application;

FIG. 8 schematically shows a schematic structural diagram of a metadata database management apparatus provided by some embodiments of the present application;

Figure 9 schematically shows a block diagram of a computing processing device for performing methods according to some embodiments of the present application;

Figure 10 schematically shows a storage unit for holding or carrying program code implementing methods according to some embodiments of the present application.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

FIG. 1 schematically shows a metadata database management method provided by the present application, which is applied to a metadata database management terminal, and the metadata database management terminal is connected to a plurality of metadata database nodes. The method includes:

It should be noted that metadata refers to the structured data (such as title, edition, publication data, relevant descriptions, including access points, etc.) extracted from information resources to describe its characteristics and content, and is used to organize , describe, retrieve, store, and manage information and knowledge resources. For example, our company's various servers, terminals, industries, projects, cooperative hospitals, platforms, platform users, permissions, roles, log types, administrative divisions, business alarm types and other information, the metadata database node is used to store metadata. Database node, metabase node can be a distributed database, so there can be multiple metabase nodes. The metadata database management terminal is a server or terminal equipment with functions such as data processing, data transmission, and data storage, such as personal computers, tablet computers, portable mobile devices, etc., which are used to manage the data of the connected metadata database nodes and the update of database versions. etc., the metadata database server can communicate with multiple metadata database nodes through the Internet of Things or the Internet. When different metabase nodes access the metabase management terminal, they need to register and enter their own information, and at least need to enter the dependent metabase version, script information and version deployment records, where the dependent metabase version is the reference required for the operation of the metabase node. Or depend on the metadata version, the script information is the script program required for the deployment of different metadata versions, and the version deployment record refers to the historical record of the metabase version deployed by the metabase script.

Step 101, in response to a version change operation for at least one metabase node among the plurality of metabase nodes, determine a target metabase version corresponding to the version change operation.

In the embodiment of the present application, when a user needs to change the version of a certain target metabase node, a version change operation can be performed on the metabase management terminal. The target metabase node indicated by the version change operation is determined in the nodes, and the target metabase version indicated by the version change operation is determined from a plurality of metabase versions. It can be understood that, in this embodiment of the present application, the previous update processes for different metadata database versions are centralized at the metadata database management end for unified management, so as to facilitate the management of version updates of different metadata database nodes.

Step 102: Determine the target dependent metabase version and target script information corresponding to the target metabase version according to the correspondence between the different metabase versions, the dependent metabase version, and the script information.

In the embodiment of the present application, since the dependent metabase versions of different metabase versions are different, if a target metabase version needs to be deployed on a target metabase node, it is necessary to know whether the dependent metabase version of the target metabase version is It has been deployed on the target metabase node, so the version deployment record can be queried for the database version-dependent deployment record of the target metabase version. After each successful deployment of a metabase version, the metabase node will display the corresponding database version in the version deployment record. Update the deployment record for this metabase version in the version deployment record.

Step 103: When there is a deployment record of the target-dependent metabase version in the target metabase node, extract a script applicable configuration and a script storage address from the target script information.

In the embodiment of the present application, if the target metabase version has not been deployed on the target metabase version dependent metabase version, the deployment process of the target metabase version on the target metabase node is stopped, if the target metabase node If the dependent metabase version of the target metabase version has been deployed on the server, continue to perform the deployment process of the target metabase version, that is, extract the script applicable configuration and script storage address from the script information of the target metabase version. The applicable configuration of the script refers to hardware conditions such as device model, content size, bandwidth size and other hardware conditions required to run the script, as well as software conditions such as drivers and system architecture required for the script to run, as well as the user and password logged in on the metabase node. and other permission conditions, which can be set according to actual needs, which are not limited here. The script storage address refers to the physical address where the script program code is stored.

Step 104: Obtain a script program from the script storage address when the script applicable configuration matches the configuration information of the target metadata database node.

In the embodiment of the present application, the metabase management terminal obtains its configuration information from the target metabase node or reads the pre-stored configuration information from the database of the present application, and compares the configuration information with the script applicable configuration. If the configuration information of the database node is completely consistent with the applicable configuration of the script, the script program can be further read from the script storage address for subsequent deployment of the target metabase version.

Specifically, referring to FIG. 2, when upgrading, select the version number to be upgraded, and then detect whether the dependent version of this version has been deployed. If the dependent version does not exist, the upgrade will not be performed; if it exists, execute the version in the version one by one. For all SQL (StructuredQueryLanguage, Structured Query Language) scripts, before executing each SQL script, check whether the script's applicable architecture matches the node's architecture, and compare the script's applicable environment with the node's environment information. If it matches, the SQL script is parsed and each SQL statement in the script is executed. If one of the conditions does not match, the script is ignored and not executed. All SQL of a version is submitted as a transaction. If there is an error in executing a SQL statement in this version, all SQL will be rolled back; if all SQL statements in this version are successfully executed, insert into the version table in the database Version record, indicating that the node has been upgraded to this version.

Step 105: Execute the script program to deploy the target metabase version on the target metabase node.

In the embodiment of the present application, the metadata database management terminal executes all script programs of the target metadata version one by one, and before executing each script program, detects whether the applicable schema of the script matches the schema of the target metadata database node, and compares the Whether the applicable configuration information of the script and the configuration information of the target metabase node are configured, if they match, continue to parse the script program and continue to execute the script program. This script is ignored and the next script is executed directly. All script programs of a target metabase version are submitted as a transaction. If there is an error in executing a script program in the target metabase version, all script programs will be rolled back. If all script programs in the target metabase version are If the execution is successful, insert the version deployment record of the target metabase version into the version deployment record of the target metabase node, indicating that the target metabase node has deployed the target metabase version, that is, in the target metabase that needs to be deployed, There is a version table specially used to save version deployment records. Every time a version is deployed, a version deployment record is inserted into the version table.

In this embodiment of the present application, the metadata version update process is centralized to the metadata database management terminal for unified management, so that when the metadata database node connected to the metadata database management terminal performs data update, it is first confirmed that the metadata database node has the target metadata database to be updated. The version corresponding to the dependent metabase version, to ensure that the deployed version can be supported by the dependent metabase version, and then confirm that the configuration information of the metabase node matches the script applicable configuration of the target metabase node, and then execute the script program to deploy The target metabase version ensures that the metabase version can run normally after deployment, and if a problem occurs, it can be quickly checked through the version deployment record on the metadata management side.

Optionally, referring to FIG. 3 , the corresponding relationship between the metadata version and the script information is constructed through the following steps 201 to 204:

Step 201, in response to the corresponding relationship construction instruction, display a version tree including the hierarchical relationship between the metadata database versions.

In this embodiment of the present application, the metadata version may be a large version or a small version, the difference is that no script information is added to the large version, and the large version of the metadata version can be deployed through the script information of the small version of the metadata database version. Therefore, the relationship between the upper and lower levels of the metadata database versions can be represented by means of a version tree.

In practical applications, the user can view the version data on the display node of the metadata management terminal, so as to select the node where the metadata version to be updated is located on the version data to create the metadata database version. If the selected node is the root node , it indicates that a major version is created. If the selected node is a major version, the metadata version of the minor version is created.

Step 202 , in response to a new operation on any version parent node in the version tree, create a version child node subordinate to the version parent node, and acquire and store metadata database version information.

In the embodiment of the present application, when creating a metabase version, the user needs to input the attribute information of the metabase version to be created in the metabase management terminal, the attribute information includes the version number, the associated product name plus the version number, version description information, docking The developer information, creation time, and version number depending on the metadata database version, etc., can be set according to actual needs, and there are no restrictions here.

Step 203: Acquire and store script information in response to the script entry operation for the metadata database version information.

In the embodiment of the present application, the metadata database management terminal will enter the attribute information input by the user into the version library. If the created metadata version is a major version, the creation is complete, and there is no need to continue entering script information. If the created metabase version is a minor version, after the version is created, add script information for the metabase version. When adding script information, you need to set the attribute information of the script, including the applicable configuration of the script, the metadata database identifier executed by the script, the mapping database identifier, the script storage address, etc. The applicable configuration of the script includes the applicable script structure and the script applicable environment. The actual demand settings are not limited here.

Step 204: Associate and store the metadata database version information and the script information.

In the embodiment of the present application, after the addition of script information is completed, the metabase management terminal will store the script information in the version library in association with the newly created metabase version, and then copy the script storage address of the script program to the version number according to the version number. Encrypted storage is carried out in the unified planning directory. In this way, multiple scripts can be added according to actual needs.

Optionally, referring to FIG. 4, after the step 201, the method further includes:

Step 301, in response to an editing operation on any target version node in the version tree, display version information and script information corresponding to the target version node.

In the embodiment of the present application, the user can edit any target version node in the script data in the display interface of the metadata database management terminal, so as to display the version information and script information corresponding to the version number in the attribute display area.

Step 302, in response to an editing operation on the version information and/or the script information, update the version information and/or the script information indicated by the editing operation.

In the embodiment of the present application, the user can rewrite the latest version information into the repository by clicking the save function option after modifying the version information and/or script information in the display interface.

The user can select the script to be modified in the script list interface of the display interface, and then modify the script information and script content, and enter the latest attribute value in each attribute box. After the modification is completed, click the save option to save the latest script information. Update to the repository.

Of course, the user can also select a script in the display interface and then click the delete option to delete the script information in the repository and delete the corresponding script file in the script directory.

Step 303, in response to the viewing operation for the script information, obtain a script program from the script storage address, and display the code information of the script program.

In the embodiment of the present application, when the user selects a script in the script tree of the display interface, data is read from the basic library, and the script information of the version is displayed on the display interface, such as: applicable environment, applicable system architecture, script application database and other attribute information, click a script information in the script list, or read data from the script library, and display the script information on the display interface, the user can click the script information to read the script information from the script directory and perform Decrypt, and then display the decrypted script information on the display interface.

Optionally, the method further includes: in response to a metadata database node creation operation, acquiring and storing metadata database node information, where the metadata database node information includes: host name, port number, maintenance personnel information, password, system architecture, project At least one of the environment and cluster node relationship.

In the embodiment of the present application, the user can click the create option in the node tree displayed on the display interface of the metadata management terminal, and then set the properties of the node to be created, including the host name, port number, maintenance personnel information, password, system architecture, The project environment, cluster node relationship, etc., can be set according to actual needs, which is not limited here. The metabase management terminal will store the attribute information and write it into the node library.

Optionally, referring to FIG. 5 , the node information of the metadata database node is edited through the following steps 401 to 403:

Step 401 , in response to the editing instruction of the metadata node information, display the metadata database node tree including the hierarchical relationship between the metadata database nodes.

Step 402: In response to an editing operation for any target metabase node identifier in the metabase node tree, display the metabase node information corresponding to the target metabase node identifier.

In the embodiment of the present application, after the node tree is displayed on the display interface of the metabase management terminal, the user can display the attribute information of the node on the display interface through the identifier of a target metabase node on the node tree.

Step 403, in response to an editing operation on the metadata database node information, update the metadata database node information.

In the embodiment of the present application, the user can click the metadata database node information of a node in the metadata database node data in the display interface, modify some of the displayed attribute information, and then click the save option to save the The latest attribute information is updated to the node library. Of course, a certain metabase node can also be deleted, so as to delete the metabase node from the node tree and the node library.

Further, referring to Fig. 6, in which the metadata database management terminal can perform addition, deletion, modification and query operations on the metadata database version and metadata nodes in the above description, and can also click a node in the interface node tree, click on the historical version interface, and the connection will be made. The node database reads version records from the version table and displays them on the interface. Click a node in the interface node tree, right-click to select the backup library option, the database backup program will be called, and the database will be backed up to the specified address. Click a node in the interface node tree, right-click to select the restore library option, call the restore program of the database, read the selected restore script, and then restore the database to the historical state.

Optionally, the step 101 includes: when there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, changing the intermediate The metabase version and the metabase version indicated by the version change operation are taken as the target metabase version.

In this embodiment of the present application, if the metabase version indicated by the version change operation is not adjacent to the current metabase version currently deployed by the target metabase node, that is, there is at least one level between the two versions that is higher than the current metabase version. A metabase version that is higher than the level of the metabase version indicated by the version change operation cannot be updated directly from the current metabase version to the metabase version indicated by the operation. At this time, it can be determined that the metabase version and the intermediate metabase version indicated by the version change operation are both the target metabase version, and the target metabase nodes are updated in sequence according to the version level sequence relationship between multiple target metabase versions. ,

Optionally, with reference to FIG. 7 , a flowchart of steps of another metadata database management method provided by an embodiment of the present application is shown:

Step 501, in response to a version change operation for at least one metabase node among the plurality of metabase nodes, there is an existence between the metabase version indicated by the version change operation and the current metabase version of the target metabase node. When there is at least one intermediate metabase version, the intermediate metabase version and the metabase version indicated by the version change operation are used as the metabase version to be updated.

In the embodiment of the present application, there is usually a dependency relationship between metabase versions at different levels, so the lower-level metabase version needs to be deployed on the target metabase node before continuing to deploy the higher-level metabase version.

Specifically, in the actual update process, first, both the metabase version and the intermediate metabase version indicated by the version change operation are used as the metabase version to be updated for subsequent version updates one by one.

In step 502, the metadata database version to be updated with the lowest database version level is used as the target metadata database version.

In the embodiment of the present application, since the low-level metabase version may be a dependent metabase version of the high-level metabase version, the present application takes the version with the lowest version level among the to-be-updated metabase versions as the target of this version update Metabase version. It should be noted that the level of the metabase version here does not refer to the release time of the metabase version, but the dependency between the metabase versions. The lower the dependency, the lower the level of the metabase version, and vice versa. The higher the relationship level, the higher the level of the metabase version. For example, there are metabase version 1, metabase version 2, and metabase version 3 with later distribution times. Metabase version 1 is the dependent metabase version of metabase version 2. However, metabase version 3 is the latest version of the dependent metabase version of metabase version 1. Therefore, metabase version 3 is also the dependent source database version of metabase version 1. The order of the version levels from low to high is: metabase version 3. Metabase Version 1, Metabase Version 2. Of course, this is only an exemplary description, and the specific hierarchical relationship can be set according to actual requirements, which is not limited here.

Step 503: Determine the target-dependent metabase version and target script information corresponding to the target metabase version according to the correspondence between the different metabase versions, the dependent metabase version, and the script information.

For this step, reference may be made to the detailed description of step 102, which will not be repeated here.

Step 504 , when there is a deployment record of the target-dependent metabase version in the target metabase node, extract the script applicable configuration and the script storage address from the target script information.

For this step, reference may be made to the detailed description of step 103, which will not be repeated here.

Step 505: Obtain a script program from the script storage address when the script applicable configuration matches the configuration information of the target metadata database node.

For this step, reference may be made to the detailed description of step 104, which will not be repeated here.

Step 506: Execute the script program to deploy the target metabase version on the target metabase node.

For this step, reference may be made to the detailed description of step 105, which will not be repeated here.

Step 507: Remove the target metabase version from the metabase version to be updated, and re-enter the step of using the lowest level metabase version to be updated as the target metabase version, until the metabase version to be updated does not exist. When the database version is reached, the version update process for the target metadata database node is ended.

In the embodiment of the present application, after the target database version is successfully updated, the version with the lowest level is continued to be selected from the remaining unupdated to-be-updated metadata database versions as the next target metadata database version to be updated and modified, so that according to the version level The relationship proceeds from low to high metabase version until the metabase version indicated by the version update operation is updated.

Step 508 , when the update of the target metabase version fails, roll back the updated content for the target metabase version, and end the execution of the version update process for the target metabase node.

In the application embodiment, if there is no deployment record of the target-dependent metabase version in the target metabase node during the update process, or if the script applicable configuration does not match the configuration information of the target metabase node, It is determined that the update of the target metabase version fails. At this time, all previous updates to the target metabase version are rolled back and restored to the initial metabase version of the target metabase before the version update, that is, the current metabase version in the above description.

In this embodiment of the present application, in the process of metabase cross-version update, the update is performed in order from low to high according to the version hierarchy relationship between the to-be-updated metabase versions, which ensures that there is no dependency on the metabase version during the process of metadata cross-version update. , which improves the stability of metadata versions.

8 schematically shows a schematic structural diagram of a metadata database management device 60 provided by the present application, which is applied to a metadata database management terminal. The metadata database management terminal is connected to a plurality of metadata database nodes, and the device includes:

An input module 601, configured to, in response to a version change operation for at least one metabase node in the plurality of metadata database nodes, determine a target metadata database version corresponding to the version change operation;

A verification module 602, configured to determine the target-dependent metabase version and target script information corresponding to the target metabase version according to the correspondence between different metabase versions and the dependent metabase version and script information;

When there is a deployment record of the target-dependent metabase version in the target metabase node, extracting a script applicable configuration and a script storage address from the target script information;

Obtaining a script program from the script storage address when the script applicable configuration matches the configuration information of the target metabase node;

The deployment module 603 is configured to execute the script program, and deploy the target metabase version on the target metabase node.

Optionally, the device further includes: an editing module for:

In response to the construction instruction of the corresponding relationship, displaying a version tree containing the hierarchical relationship between the metadata database versions;

In response to the newly added operation to any version parent node in the version tree, create a version child node subordinate to the version parent node, and obtain and store the metadata database version information;

Acquire and store script information in response to a script entry operation for the metabase version information;

The metadata database version information and the script information are associated and stored.

Optionally, the editing module is also used for:

In response to an editing operation on any target version node in the version tree, displaying version information and script information corresponding to the target version node;

In response to an editing operation on the version information and/or the script information, the version information and/or the script information indicated by the editing operation is updated.

Optionally, the verification module 602 is further configured to, when there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, verify the The intermediate metabase version and the metabase version indicated by the version change operation are used as the target metabase version.

Optionally, the verification module 602 is also used for:

When there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, change the intermediate metabase version and the version indicated by the version change operation The metabase version of the to-be-updated metabase version;

Use the metabase version to be updated with the lowest database version level as the target metabase version;

Remove the target metabase version from the to-be-updated metabase version, and re-enter the step of using the lowest-level metabase version to be updated as the target metabase version, until the to-be-updated metabase version does not exist , and finish executing the version update process for the target metabase node.

Optionally, the deployment module 603 is further configured to:

When the update of the target metabase version fails, the updated content for the target metabase version is rolled back, and the execution of the version update process for the target metabase node is ended.

Optionally, the editing module is also used for:

In response to the editing instruction of the metadata node information, displaying the metadata database node tree including the hierarchical relationship between the metadata database nodes;

In response to an editing operation for any target metabase node identifier in the metabase node tree, displaying the metabase node information corresponding to the target metabase node identifier;

The metabase node information is updated in response to an edit operation on the metabase node information.

In this embodiment of the present application, the metadata version update process is centralized to the metadata database management terminal for unified management, so that when the metadata database node connected to the metadata database management terminal performs data update, it is first confirmed that the metadata database node has the target metadata database to be updated. The version corresponding to the dependent metabase version, to ensure that the deployed version can be supported by the dependent metabase version, and then confirm that the configuration information of the metabase node matches the script applicable configuration of the target metabase node, and then execute the script program to deploy The target metabase version ensures that the metabase version can run normally after deployment, and if a problem occurs, it can be quickly checked through the version deployment record on the metadata management side.

The device embodiments described above are only illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed over multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. Those of ordinary skill in the art can understand and implement it without creative effort.

Various component embodiments of the present application may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in the computing processing device according to the embodiments of the present application. The present application can also be implemented as an apparatus or apparatus program (eg, computer programs and computer program products) for performing part or all of the methods described herein. Such a program implementing the present application may be stored on a computer-readable medium, or may be in the form of one or more signals. Such signals may be downloaded from Internet sites, or provided on carrier signals, or in any other form.

For example, Figure 9 shows a computing processing device that can implement methods according to the present application. The computing processing device traditionally includes a processor 710 and a computer program product or computer readable medium in the form of a memory 720 . The memory 720 may be electronic memory such as flash memory, EEPROM (electrically erasable programmable read only memory), EPROM, hard disk, or ROM. The memory 720 has storage space 730 for program code 731 for performing any of the method steps in the above-described methods. For example, storage space 730 for program code may include individual program codes 731 for implementing various steps in the above methods, respectively. The program codes can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. Such computer program products are typically portable or fixed storage units as described with reference to FIG. 10 . The storage unit may have storage segments, storage spaces, etc. arranged similarly to the memory 720 in the computing processing device of FIG. 9 . The program code may, for example, be compressed in a suitable form. Typically, the storage unit includes computer readable code 731', ie code readable by a processor such as 710 for example, which when executed by a computing processing device, causes the computing processing device to perform any of the methods described above. of the various steps.

It should be understood that although the various steps in the flowchart of the accompanying drawings are sequentially shown in the order indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order and may be performed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution sequence is also It does not have to be performed sequentially, but may be performed alternately or alternately with other steps or at least a portion of sub-steps or stages of other steps.

Reference herein to "one embodiment," "an embodiment," or "one or more embodiments" means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment of the present application. Also, please note that instances of the phrase "in one embodiment" herein are not necessarily all referring to the same embodiment.

In the description provided herein, numerous specific details are set forth. It will be understood, however, that the embodiments of the present application may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. do not denote any order. These words can be interpreted as names.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be The technical solutions described in the foregoing embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present application.

Claims (10)

1. A method for managing a metabase, characterized in that it is applied to a metabase management terminal, which is connected to a plurality of metabase nodes, the method comprising: In response to a version change operation for at least one metabase node in the plurality of metabase nodes, determining a target metabase version corresponding to the version change operation; Determine the target dependent metabase version and target script information corresponding to the target metabase version according to the correspondence between different metabase versions, dependent metabase versions, and script information; When there is a deployment record of the target-dependent metabase version in the target metabase node, extracting a script applicable configuration and a script storage address from the target script information; Obtaining a script program from the script storage address when the script applicable configuration matches the configuration information of the target metabase node; The script program is executed to deploy the target metabase version on the target metabase node. 2. The method according to claim 1, wherein the correspondence between the metadata version and the script information is constructed by the following steps: In response to the construction instruction of the corresponding relationship, displaying a version tree containing the hierarchical relationship between the metadata database versions; In response to the newly added operation to any version parent node in the version tree, create a version child node subordinate to the version parent node, and obtain and store the metadata database version information; Acquire and store script information in response to a script entry operation for the metabase version information; The metadata database version information and the script information are associated and stored. 3. The method according to claim 2, characterized in that, after displaying the version tree containing the association relationship between the metadata database versions, the method further comprises: In response to an editing operation on any target version node in the version tree, displaying version information and script information corresponding to the target version node; In response to an editing operation on the version information and/or the script information, the version information and/or the script information indicated by the editing operation is updated. 4. The method according to claim 1, wherein the determining the target metadata database version corresponding to the version change operation comprises: When there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, change the intermediate metabase version and the version indicated by the version change operation The metabase version of the target metabase version. 5. The method according to claim 4, wherein the taking the intermediate metabase version and the metabase version indicated by the version change operation as the target metabase version comprises: When there is at least one intermediate metabase version between the metabase version indicated by the version change operation and the current metabase version of the target metabase node, change the intermediate metabase version and the version indicated by the version change operation The metabase version of the to-be-updated metabase version; Use the metabase version to be updated with the lowest database version level as the target metabase version; After the executing the script program, after the target metabase node deploys the target metabase version, the method further includes: Remove the target metabase version from the to-be-updated metabase version, and re-enter the step of using the lowest-level metabase version to be updated as the target metabase version, until the to-be-updated metabase version does not exist , and finish executing the version update process for the target metabase node. 6. The method according to claim 5, wherein after the metabase version to be updated with the lowest database version level is taken as the target metabase version, the method further comprises: When the update of the target metabase version fails, the updated content for the target metabase version is rolled back, and the execution of the version update process for the target metabase node is ended. 7. The method according to claim 1, wherein the node information of the metadata database node is edited by the following steps: In response to the editing instruction of the metadata node information, displaying the metadata database node tree including the hierarchical relationship between the metadata database nodes; In response to an editing operation for any target metabase node identifier in the metabase node tree, displaying the metabase node information corresponding to the target metabase node identifier; The metabase node information is updated in response to an edit operation on the metabase node information. 8. A metadata database management device, characterized in that it is applied to a metadata database management terminal, the metadata database management terminal is connected to a plurality of metadata database nodes, and the device comprises: an input module, configured to, in response to a version change operation for at least one metabase node in the plurality of metabase nodes, determine a target metabase version corresponding to the version change operation; a verification module, configured to determine the target-dependent metabase version and target script information corresponding to the target metabase version according to the correspondence between different metabase versions and the dependent metabase version and script information; When there is a deployment record of the target-dependent metabase version in the target metabase node, extracting a script applicable configuration and a script storage address from the target script information; Obtaining a script program from the script storage address when the script applicable configuration matches the configuration information of the target metabase node; A deployment module, configured to execute the script program, and deploy the target metabase version on the target metabase node. 9. A computing and processing device, comprising: a memory in which computer readable code is stored; One or more processors, when the computer readable code is executed by the one or more processors, the computing processing device executes the metadata database management method according to any one of claims 1 to 7 . 10. A computer-readable medium, wherein the metadata database management method according to any one of claims 1 to 7 is stored therein.

Images