Metadata management method and device, electronic equipment and computer storage medium

Abstract

The application provides a metadata management method and device, electronic equipment and computer storage medium. The method comprises the following steps: firstly, completing the addition of a meta model to obtain an added meta model; then, registering registration information of file type data of the added meta model; wherein the registration information comprises basic information, a data source, field information, security information, management information and file transfer protocol information; then, performing collection configuration on the added meta model; wherein the collection configuration comprises a collection data source, a collection adapter and collection job information; then, collecting metadata according to the collection configuration; finally, storing the collected registration metadata and collection metadata; wherein the storage mode of the registration metadata and the collection metadata is the same storage structure, and the metadata type, the meta model number and the metadata name are used as the unique primary key to identify a metadata. The completeness of metadata management is effectively improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a metadata management method and device, electronic equipment and computer storage medium. BACKGROUND

[0002] There are two kinds of metadata management methods in prior art, designed metadata management and implemented metadata management. Both of the two kinds of metadata management methods need to manage meta model and collect relevant metadata information according to the meta model. The difference lies in that the designed metadata management controls in the data design link, which is mainly realized by manually filling in forms or meta model template documents; the implemented metadata management manages after the data landing link, which is mainly realized by configuring different types of collection adapters to realize automatic collection of metadata. Among them, the designed metadata management needs strong management support to form a strong driving force from top to bottom, and strictly completes the collection of metadata according to the relevant process. The disadvantage of this method is that it relies too much on management strength and manual maintenance, which is high in labor cost and cannot effectively guarantee the continuity, accuracy and integrity of metadata management; the implemented metadata management collects metadata through technical means after the data landing, which can guarantee the high consistency of the collected metadata with the production environment, but due to the limitation of the production environment, part of the business metadata and management metadata cannot be obtained through technical means, and part of the technical methods consider adding manual supplement to solve this problem, which will inevitably reduce the work efficiency and make it difficult to guarantee the integrity of metadata management. SUMMARY

[0003] Therefore, the present application provides a metadata management method and device, electronic equipment and computer storage medium, which can effectively improve the integrity of metadata management.

[0004] The first aspect of the present application provides a metadata management method, comprising:

[0005] completing the addition of the meta model to obtain an added meta model;

[0006] registering registration information of file class data of the added meta model; wherein the registration information comprises basic information, data source, field message, security information, management information and file transfer protocol information;

[0007] configuring collection of the added meta model; wherein the collection configuration comprises collection data source, collection adapter and collection job information;

[0008] the added meta model collects metadata according to the collection configuration;

[0009] The collected registration metadata and collection metadata are stored; wherein the storage manners of the registration metadata and the collection metadata are the same storage structure, and a metadata type, a meta model number and a metadata name are used as a unique primary key to identify one metadata.

[0010] Optionally, the adding of the meta model is completed to obtain an added meta model, and the method comprises the following steps.

[0011] According to the current inventory meta model, the number of the added meta model is determined.

[0012] Attribute information of the added meta model is defined, wherein the attribute information comprises a name, technical attribute, business attribute, management attribute, security attribute, operation attribute and dependency information.

[0013] The adding of the added meta model is completed.

[0014] Optionally, the collection configuration of the added meta model comprises the following steps.

[0015] According to the development and production environment, a collection data source is configured.

[0016] According to the type of the relational data warehouse, a corresponding collection adapter is selected.

[0017] Collection job information is configured, wherein the collection job information comprises a collection job name and a collection job execution frequency.

[0018] Optionally, after the storage of the collected registration metadata and collection metadata, the method further comprises the following steps.

[0019] For each metadata, the registration metadata and the collection metadata collected in the registration and collection processes are compared according to a comparison rule of the metadata to obtain a comparison result.

[0020] If the comparison result shows that the registration metadata and the collection metadata are different, a difference analysis report is generated.

[0021] If the comparison result shows that the registration metadata and the collection metadata are the same, the registration metadata and the collection metadata of the next metadata are compared.

[0022] The second aspect of the application provides a metadata management device, comprising:

[0023] A model adding unit is configured to complete the adding of the meta model to obtain an added meta model.

[0024] A registration unit is configured to register registration information of file class data of the new meta model; the registration information includes basic information, a data source, field information, security information, management information, and file transfer protocol information;

[0025] A configuration unit is configured to perform collection configuration on the new meta model; the collection configuration includes a collection data source, a collection adapter, and collection job information;

[0026] A collection unit is configured to perform collection of metadata according to the collection configuration of the new meta model;

[0027] A storage unit is configured to store the collected registration metadata and collection metadata; the storage mode of the registration metadata and the collection metadata is the same storage structure, and a metadata type, a meta model number, and a metadata name are used as unique primary keys to identify one metadata.

[0028] Optionally, the model adding unit includes:

[0029] A number determination unit is configured to determine a number of the new meta model according to current inventory meta models;

[0030] A definition unit is configured to define attribute information of the new meta model; the attribute information includes a name, technical attributes, business attributes, management attributes, security attributes, operation attributes, and dependency information;

[0031] A model adding subunit is configured to complete addition of the new meta model.

[0032] Optionally, the configuration unit includes:

[0033] A first configuration subunit is configured to configure a collection data source according to a development and production environment;

[0034] A second configuration subunit is configured to select a corresponding collection adapter according to a type of a relational data warehouse;

[0035] A third configuration subunit is configured to configure collection job information; the collection job information includes a collection job name and a collection job execution frequency.

[0036] Optionally, the metadata management device further includes:

[0037] A comparison unit is configured to compare, for each metadata, registration metadata and collection metadata collected in a registration and collection process according to a comparison rule of the metadata to obtain a comparison result;

[0038] The generating unit generates a difference analysis report if the comparison result indicates that the registered metadata and the collected metadata are different.

[0039] The processing unit compares the registered metadata and the collected metadata of the next metadata if the comparison result indicates that the registered metadata and the collected metadata are the same.

[0040] The third aspect of the present application provides an electronic device, comprising:

[0041] one or more processors;

[0042] a storage device having one or more programs stored thereon;

[0043] The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the metadata management method according to any one of the first aspect.

[0044] The fourth aspect of the present application provides a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the metadata management method according to any one of the first aspect.

[0045] From the above solution, the present application provides a metadata management method, device, electronic device and computer storage medium. The metadata management method comprises the following steps: firstly, adding a new meta model to obtain a new meta model; then, registering registration information of file data of the new meta model; the registration information comprises basic information, data source, field message, security information, management information and file transfer protocol information; then, performing collection configuration on the new meta model; the collection configuration comprises collection data source, collection adapter and collection job information; then, collecting metadata according to the collection configuration; finally, storing the collected registered metadata and collected metadata; the storage mode of the registered metadata and the collected metadata is the same storage structure, and the metadata type, the meta model number and the metadata name are used as the unique primary key to identify a metadata. The registered metadata and the collected metadata are organically combined to realize metadata management, and the completeness of metadata management is effectively improved through the integration of the registered metadata and the collected metadata. BRIEF DESCRIPTION OF DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only embodiments of the present application, and those skilled in the art can obtain other drawings according to the provided drawings without creative labor.

[0047] Figure 1 A specific flowchart of a metadata management method provided for an embodiment of the present application is shown in FIG. 1;

[0048] Figure 2 A flowchart of a metadata management method provided for another embodiment of the present application is shown in FIG. 2;

[0049] Figure 3 A flowchart of a metadata management method provided for another embodiment of the present application is shown in FIG. 3;

[0050] Figure 4 A flowchart of a metadata management method provided for another embodiment of the present application is shown in FIG. 4;

[0051] Figure 5 A schematic diagram of a metadata management device provided for another embodiment of the present application is shown in FIG. 5;

[0052] Figure 6 A schematic diagram of a model adding unit provided for another embodiment of the present application is shown in FIG. 6;

[0053] Figure 7 A schematic diagram of a configuration unit provided for another embodiment of the present application is shown in FIG. 7;

[0054] Figure 8 A schematic diagram of a metadata management device provided for another embodiment of the present application is shown in FIG. 8;

[0055] Figure 9 A schematic diagram of an electronic device implementing a metadata management method provided for another embodiment of the present application is shown in FIG. 9. DETAILED DESCRIPTION

[0056] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0057] The term “comprising” and variations thereof as used in the present document are open-ended, that is, “including but not limited to”. The term “based on” is “at least in part based on”. The term “one embodiment” means “at least one embodiment”; the term “another embodiment” means “at least one additional embodiment”; the term “some embodiments” means “at least some embodiments”. Related definitions of other terms will be given in the following description.

[0058] It should be noted that the "first", "second", and the like mentioned in the present application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0059] It should be noted that the "one", "multiple" modification mentioned in the present application is illustrative but not restrictive, and those skilled in the art should understand that unless the context clearly indicates otherwise, it should be understood as "one or more".

[0060] The embodiment of the present application provides a kind of generation of alarm information method, as shown in Figure 1 Specifically includes the following steps:

[0061] S101, complete the addition of meta model, obtain the newly added meta model.

[0062] Optionally, in another embodiment of the present application, an embodiment of step S101, as shown in Figure 2 Specifically includes:

[0063] S201, determine the number of newly added meta model according to current inventory meta model.

[0064] Specifically, the number of newly added meta model can be but not limited to the maximum number of current inventory meta model plus 1, which is not limited here.

[0065] S202, define the attribute information of newly added meta model.

[0066] Among them, attribute information includes: name, technical attribute, business attribute, management attribute, security attribute, operation attribute and dependency information.

[0067] Among them, name can be defined as relational database table and the like; technical attribute includes but is not limited to library table physical name, and technical attribute rule can be further defined, for example: the naming rule of library table physical name should comply with "data layer_theme domain_business description"; business attribute includes but is not limited to "library table Chinese name", "library table English name", "library table description" and the like; management attribute includes but is not limited to "responsible department", "person in charge", "creation date", "audit cycle", "save cycle" and the like; security attribute includes but is not limited to "update frequency", "access times", "library table inventory space", "library table incremental space" and the like; dependency information includes but is not limited to "relational database table" and "relational database field", "relational database index" and the like have dependency relationship, which is not limited here. As shown in table 1, it is part of the directory structure of meta model. Dependency information includes inheritance relationship, combination relationship and dependency relationship.

[0068] Primary directory Secondary directory Tertiary directory Meta model name Data collection Batch File Data file Real-time Message queue Message queue Data storage Relational database Oracle Library table Field NoSQL database HIVE Library table Data processing Batch processing ETL Processing task Stream processing Spark Processing task Data service Batch File Data file Real-time Message queue Message queue

[0069] Table 1

[0070] S203, completing the addition of the added meta model.

[0071] S102, registering registration information of the file class data of the added meta model.

[0072] The registration information includes basic information, data source, field message, security information, management information, and file transfer protocol information. The basic information includes but is not limited to "data belonging to business classification", "data name", "data content brief", "data collection frequency", etc. More preferably, through preset configuration management, part of the information can be registered through point selection operation, improving efficiency and system usability; the data source, as important information of the data collection link, needs to record the business system of the data source; more preferably, the field message can support uploading of related file field description documents, or can support association and reference of data standards to further improve the standardization of the metadata; the security information, such as whether to contain the established privacy information through point selection, can automatically generate the security level of the file class data; the management information includes but is not limited to "responsible department", "responsible person", etc., which is not limited here.

[0073] It should be noted that the registration of the metadata can be performed in the data design link. Moreover, the addition, modification, and deletion operations of the metadata are supported. The configuration management of the related metadata attributes is supported, and the reference association of the data standards is supported, reducing manual operation and improving efficiency and quality.

[0074] S103, collecting configuration of the added meta model.

[0075] The collection configuration includes collection data source, collection adapter, and collection job information.

[0076] Optionally, in another embodiment of the present application, an embodiment of step S103 includes the following steps as shown in Figure 3

[0077] S301, collecting data source according to development and production environment configuration.

[0078] For example, for the collection of the relational data warehouse, the IP address of the server where the data warehouse is located, the data warehouse name, etc. need to be configured.

[0079] S302, selecting a corresponding collection adapter according to the type of the relational data warehouse.

[0080] For example, Oracle collection adapter, GreenPlum collection adapter, EDB collection adapter, etc.

[0081] S303, configuring collection job information. ​

[0082] The collection task information includes a collection task name and a collection task execution frequency.

[0083] In the actual application of the present application, monitoring of the collection task can be added, and the running state of the task is monitored, and the task that does not run normally is alarmed.

[0084] S104, the new meta model collects metadata according to the collection configuration.

[0085] S105, the collected registration metadata and collection metadata are stored.

[0086] The storage mode of the registration metadata and the collection metadata is the same storage structure, and the metadata type, the meta model number and the metadata name are used as the unique primary key to identify a metadata.

[0087] In the actual application of the present application, the metadata update processing mechanism also needs to be considered. Generally, there are two update mechanisms, full update and incremental update. The appropriate update mechanism needs to be selected according to the actual application scene such as the metadata volume.

[0088] Optionally, in another embodiment of the present application, an embodiment of the metadata management method, as shown in Figure 4 includes:

[0089] S401, for each metadata, the registration metadata and the collection metadata collected in the registration and collection process are compared according to the comparison rule of the metadata, and the comparison result is obtained.

[0090] Due to the inherent difference between the registration metadata and the collection metadata, there must be a meta model attribute that cannot be strictly compared. Therefore, it is necessary to specify which field is the key field that needs to be strongly consistent, which field can have a difference, and which field does not participate in comparison.

[0091] It should be noted that the comparison rule is set, changed by a technician or a relevant authorized staff, which is not limited here.

[0092] Specifically, the comparison method can be from statistics to details, matching the number, attributes and contents of the two sets of metadata. Taking the library table of the relational data warehouse as an example, the library table "physical name", "library table Chinese name", "field number", "field physical name", "field description" and "update frequency" are matched.

[0093] S402, if the comparison result shows that the registration metadata and the collection metadata are not the same, a difference analysis report is generated.

[0094] S403, if the comparison result shows that the registration metadata and the collection metadata are the same, then the comparison of the registration metadata and the collection metadata of the next metadata is performed.

[0095] It should be noted that in the specific implementation process of the present application, the monitoring and alarm function of the difference between the registration metadata and the collection metadata can also be supported.

[0096] In the specific implementation process of the present application, the integration rule of the registration metadata and the collection metadata can also be defined. The integration rule is that the registration metadata is the main data source and the collection metadata is the auxiliary data source. According to the directory structure of the meta model, the integration of the registration metadata and the collection metadata is performed level by level and class by class to form a unified view of the metadata and support the query of the metadata. When there is a conflict between the registration metadata and the collection metadata, the registration metadata is used as the standard, and for the metadata that cannot be obtained in the registration metadata, the metadata obtained by the collection metadata is used for supplement.

[0097] From the above scheme, it can be known that the present application provides a metadata management method: first, the addition of the meta model is completed to obtain the added meta model; then, the registration information of the file class data of the added meta model is registered; wherein the registration information includes basic information, data source, field message, security information, management information and file transfer protocol information; then the added meta model is collected and configured; wherein the collection configuration includes collection data source, collection adapter and collection job information; then the added meta model collects metadata according to the collection configuration; finally, the collected registration metadata and collection metadata are stored; wherein the storage mode of the registration metadata and the collection metadata is the same storage structure, and the metadata type, the meta model number and the metadata name are used as the unique primary key to identify a metadata. The registration metadata and the collection metadata are organically combined to realize the management of the metadata, and the integration of the registration metadata and the collection metadata is supplemented, so that the completeness of the metadata management is effectively improved.

[0098] The computer program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). The application is described in the general context of method steps that can be implemented in one embodiment by a program executing on a computer or a processor of a computer program product. The program can be implemented in assembly or machine language, if desired. In this

[0099] The names of messages or information exchanged between the plurality of apparatuses in the embodiments of the present application are used only for illustrative purposes, and are not intended to limit the scope of the messages or information.

[0100] Computer program code for carrying out operations of the present application can be written in one or more programming languages or combinations of languages including object oriented, scripting and conventional procedural programming languages, such as Python, Java, C++, or the like. Program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0101] Another embodiment of the present application provides a metadata management apparatus, as shown in Figure 5 specifically comprising:

[0102] The model adding unit 501 is configured to add a meta model to obtain an added meta model.

[0103] Optionally, in another embodiment of the present application, an implementation of the model adding unit 501 includes, as shown in Figure 6

[0104] The number determining unit 601 is configured to determine the number of the added meta model according to the current inventory meta model.​

[0105] Define unit 602, which is used to define the attribute information of the newly added metamodel.

[0106] The attribute information includes: name, technical attributes, business attributes, management attributes, security attributes, operational attributes, and dependency information.

[0107] The model adds sub-unit 603 to complete the addition of the new meta-model.

[0108] For details on the specific working process of the units disclosed in the above embodiments of this application, please refer to the corresponding method embodiments, such as... Figure 2 As shown, it will not be elaborated further here.

[0109] Registration unit 502 is used to register the registration information of file-type data for newly added meta-models.

[0110] The registration information includes basic information, data source, field messages, security information, management information, and file transfer protocol information.

[0111] Configuration unit 503 is used to collect and configure new meta-models.

[0112] The data acquisition configuration includes the data acquisition data source, the data acquisition adapter, and the data acquisition job information.

[0113] Optionally, in another embodiment of this application, one implementation of the configuration unit 503 is as follows: Figure 7 As shown, it includes:

[0114] The first configuration subunit 701 is used to configure the data source for data collection according to the development and production environment.

[0115] The second configuration subunit 702 is used to select the appropriate acquisition adapter according to the type of relational data warehouse.

[0116] The third configuration subunit 703 is used to configure data acquisition job information; the data acquisition job information includes: data acquisition job name and data acquisition job execution frequency.

[0117] For details on the specific working process of the units disclosed in the above embodiments of this application, please refer to the corresponding method embodiments, such as... Figure 3 As shown, it will not be elaborated further here.

[0118] The acquisition unit 504 is used to acquire metadata for the newly added meta-model according to the acquisition configuration.

[0119] Storage unit 505 is used to store the collected registration metadata and acquisition metadata.

[0120] The storage manners of the registration metadata and the collection metadata are the same storage structure, and each of the registration metadata and the collection metadata is identified as a metadata by taking a metadata type, a meta model number and a metadata name as a unique primary key.

[0121] The specific working processes of the units disclosed in the above embodiments of the application can be referred to the corresponding method embodiment contents, such as Figure 1 as shown, and details are not repeated here.

[0122] Optionally, in another embodiment of the application, an embodiment of the metadata management device is as shown in Figure 8 and further includes:

[0123] The comparison unit 801 is configured to compare, for each metadata, registration metadata and collection metadata collected in the registration and collection processes according to a comparison rule of the metadata, to obtain a comparison result.

[0124] The generation unit 802 is configured to generate a difference analysis report if the comparison result indicates that the registration metadata and the collection metadata are different.

[0125] The processing unit 803 is configured to compare, for each metadata, registration metadata and collection metadata if the comparison result indicates that the registration metadata and the collection metadata are the same.

[0126] The specific working processes of the units disclosed in the above embodiments of the application can be referred to the corresponding method embodiment contents, such as Figure 4 as shown, and details are not repeated here.

[0127] As can be seen from the above solutions, the application provides a metadata management device: first, the model adding unit 501 adds a meta model to obtain an added meta model; then, the registration unit 502 registers registration information of file type data of the added meta model; the registration information includes basic information, a data source, field information, security information, management information and file transfer protocol information; the configuration unit 503 configures the added meta model for collection; the collection configuration includes a collection data source, a collection adapter and collection job information; then, the collection unit 504 collects metadata according to the collection configuration; finally, the storage unit 505 stores the collected registration metadata and collection metadata; the storage manners of the registration metadata and the collection metadata are the same storage structure, and each of the registration metadata and the collection metadata is identified as a metadata by taking a metadata type, a meta model number and a metadata name as a unique primary key. The registration metadata and the collection metadata are organically combined to realize metadata management, and the integration of the registration metadata and the collection metadata is supplemented, so that the completeness of the metadata management is effectively improved.

[0128] The functionality described herein above can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program- specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

[0129] Another embodiment of the present application provides an electronic device, such as Figure 9 as shown, comprising:

[0130] one or more processors 901.

[0131] a storage 902 having stored thereon one or more programs.

[0132] The one or more programs, when executed by the one or more processors 901, enable the one or more processors 901 to implement the metadata management method according to any one of the above embodiments.

[0133] Another embodiment of the present application provides a computer storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the metadata management method according to any one of the above embodiments.

[0134] In the context of the present application, a machine-readable medium can be a tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0135] It should be noted that the computer readable medium in the foregoing of the present application can be a computer readable signal medium or a computer readable storage medium or any combination thereof. The computer readable storage medium may, for example, be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples of the computer readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, the computer readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus or device. In the present application, the computer readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer readable program code. Such a propagated data signal can take various forms, including, but not limited to, an electromagnetic signal, an optical signal or any suitable combination thereof. The computer readable signal medium can also be any computer readable medium other than the computer readable storage medium that can send, propagate or transmit the program for use by or in connection with an instruction execution system, apparatus or device. The program code contained in the computer readable medium can be transmitted by any suitable medium, including, but not limited to, a wire, an optical fiber, an RF (radio frequency) or the like, or any suitable combination thereof.

[0136] The computer readable medium described above can be contained in the electronic device described above; or can exist separately and not be assembled into the electronic device.

[0137] Another embodiment of the present application provides a computer program product, which, when executed, performs the metadata management method of any of the above.

[0138] In particular, according to embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program comprising program code for performing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network by a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, the above-mentioned functions defined in the methods of the embodiments of the present application are performed.

[0139] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0140] Although specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the application. Some of the features described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented separately or in any appropriate subcombination. For the sake of clarity, the description has not attempted to include all combinations of these various features with each other.

[0141] The above description is merely exemplary of the application and the application principles that are employed. It is to be understood that the application is not limited to the specific arrangements and instrumentalities described, since the application scope is defined in the appended claims. Other arrangements and instrumentalities can be employed without departing from the application scope. For example, the features described above can be interchanged with other features disclosed in the application (but not limited to) that have similar functionality.

Claims

1. A method of managing metadata, characterized by, The method comprises the following steps: completing addition of a meta model to obtain an added meta model; registering registration information of file class data of the added meta model; the registration information comprises basic information, data source, field message, security information, management information, and file transfer protocol information; performing collection configuration on the added meta model; the collection configuration comprises collection data source, collection adapter, and collection job information; the added meta model performs collection of metadata according to the collection configuration; storing collected registration metadata and collection metadata; the storage mode of the registration metadata and the collection metadata is the same storage structure, and a metadata type, a meta model number, and a metadata name are used as unique primary keys to identify one metadata; the registration metadata is used as a main data source, the collection metadata is used as an auxiliary data source, integration of the registration metadata and the collection metadata is performed according to a directory structure of the meta model, a unified metadata view is formed, and metadata query is supported.

2. The management method according to claim 1, characterized in that, The method of completing addition of a meta model to obtain an added meta model comprises the following steps: determining a number of the added meta model according to a current inventory meta model; defining attribute information of the added meta model; the attribute information comprises a name, technical attribute, business attribute, management attribute, security attribute, operation attribute, and dependency relationship information; completing addition of the added meta model.

3. The management method according to claim 1, characterized by, The method of performing collection configuration on the added meta model comprises the following steps: configuring a collection data source according to a development and production environment; selecting a corresponding collection adapter according to a type of a relational data warehouse; configuring collection job information; the collection job information comprises a collection job name and a collection job execution frequency.

4. The management method according to claim 1, characterized by, After the registration metadata and the collection metadata are stored, the method further comprises the following steps: for each metadata, comparing collected registration metadata and collection metadata of the metadata in a registration and collection process according to a comparison rule of the metadata to obtain a comparison result; if the comparison result shows that the registration metadata and the collection metadata are different, generating a difference analysis report; if the comparison result shows that the registration metadata and the collection metadata are the same, comparing registration metadata and collection metadata of a next metadata.

5. A metadata management apparatus characterized by comprising: The method comprises the following steps: a model addition unit is configured to complete addition of a meta model to obtain an added meta model; a registration unit is configured to register registration information of file class data of the added meta model; the registration information comprises basic information, data source, field message, security information, management information, and file transfer protocol information; a configuration unit is configured to perform collection configuration on the added meta model; the collection configuration comprises collection data source, collection adapter, and collection job information; a collection unit is configured to perform collection of metadata by the added meta model according to the collection configuration; A storage unit is configured to store the collected registration metadata and collection metadata, wherein the registration metadata and the collection metadata are stored in the same storage structure, and each metadata is identified by a metadata type, a meta-model number and a metadata name as a unique primary key; the registration metadata is used as a primary data source, and the collection metadata is used as a secondary data source; the registration metadata and the collection metadata are integrated according to a directory structure of the meta-model, a metadata unified view is formed, and metadata query is supported.

6. The management device according to claim 5, characterized by The model adding unit comprises: A number determining unit is configured to determine a number of the added meta-model according to a current inventory meta-model; A defining unit is configured to define attribute information of the added meta-model, wherein the attribute information comprises a name, technical attributes, business attributes, management attributes, security attributes, operation attributes and dependency information; A model adding sub-unit is configured to complete addition of the added meta-model.

7. The management device according to claim 5, wherein The configuration unit comprises: A first configuration sub-unit is configured to configure a collection data source according to a development and production environment; A second configuration sub-unit is configured to select a corresponding collection adapter according to a type of a relational data warehouse; A third configuration sub-unit is configured to configure collection job information, wherein the collection job information comprises a collection job name and a collection job execution frequency.

8. The management device according to claim 5, characterized by Further comprising: A comparison unit is configured to compare, for each metadata, registration metadata and collection metadata collected in a registration and collection process according to a comparison rule of the metadata to obtain a comparison result; A generation unit is configured to generate a difference analysis report if the comparison result indicates that the registration metadata and the collection metadata are different; A processing unit is configured to compare, if the comparison result indicates that the registration metadata and the collection metadata are the same, registration metadata and collection metadata of a next metadata.

9. An electronic device, comprising: One or more processors; A storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the metadata management method of any one of claims 1 to 4. A computer program is stored thereon, and the computer program is executed by a processor to implement the metadata management method of any one of claims 1 to 4.

10. A computer storage medium, characterized in that, ​

Images