CN111198902B - Metadata management method and device, storage medium and electronic equipment - Google Patents

Metadata management method and device, storage medium and electronic equipment Download PDF

Info

Publication number
CN111198902B
CN111198902B CN201811368352.7A CN201811368352A CN111198902B CN 111198902 B CN111198902 B CN 111198902B CN 201811368352 A CN201811368352 A CN 201811368352A CN 111198902 B CN111198902 B CN 111198902B
Authority
CN
China
Prior art keywords
information
metadata
difference
model
baseline data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201811368352.7A
Other languages
Chinese (zh)
Other versions
CN111198902A (en
Inventor
张辉
董亚军
张顺仕
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Changxin Memory Technologies Inc
Original Assignee
Changxin Memory Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Changxin Memory Technologies Inc filed Critical Changxin Memory Technologies Inc
Priority to CN201811368352.7A priority Critical patent/CN111198902B/en
Publication of CN111198902A publication Critical patent/CN111198902A/en
Application granted granted Critical
Publication of CN111198902B publication Critical patent/CN111198902B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30Computing systems specially adapted for manufacturing

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The present disclosure relates to a metadata management method, a metadata management apparatus, a computer-readable storage medium, and an electronic device. The metadata management method in the embodiment of the disclosure comprises the following steps: acquiring metadata information in a service system, and generating baseline data according to the metadata information; collecting metadata from the service system, and comparing the metadata with the baseline data to obtain difference comparison information; and generating management early warning information according to the difference comparison information. In the metadata management method provided by the embodiment of the disclosure, the baseline data version is generated and managed by combing the metadata information of the service system, so that the system is prevented from being bloated. The method can check the metadata of the business system by taking the newly released baseline data as a reference, and timely find out problems and early warning.

Description

Metadata management method and device, storage medium and electronic equipment
Technical Field
The disclosure relates to the technical field of databases, and in particular relates to a metadata management method, a metadata management device, a storage medium and electronic equipment.
Background
In this big data age, various types of service systems are increasing, the complexity of the service systems is also increasing, the management difficulty is increasing, and it is difficult to clearly determine the architecture of the complete service system. The service system is generally in an iterative development mode, when new service demands appear, new data forms are added in the service system, the data multiplexing is generally small, the service system scale tends to be large, and the risk of system problems is gradually increased. How to effectively manage metadata, avoid the system from being bloated, early warn and reduce the occurrence of problems in time, and improve the robustness of the system becomes a problem to be solved urgently at present.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure is directed to a metadata management method, a metadata management apparatus, a computer-readable storage medium, and an electronic device, so as to overcome, at least to some extent, the technical problems of a business system being bulky, poor in robustness, and the like caused by the limitations of the related art.
According to an aspect of the present disclosure, there is provided a metadata management method, which is characterized by comprising:
acquiring metadata information in a service system, and generating baseline data according to the metadata information;
collecting metadata from the service system, and comparing the metadata with the baseline data to obtain difference comparison information;
and generating management early warning information according to the difference comparison information.
In an exemplary embodiment of the present disclosure, the metadata information includes usage status information of the metadata;
the generating baseline data according to the metadata information comprises the following steps:
screening to obtain the metadata in use according to the use state information of the metadata;
and taking the metadata in use as production metadata, and generating baseline data according to the production metadata.
In an exemplary embodiment of the present disclosure, the metadata information further includes model state information of the metadata;
the generating baseline data from the production metadata includes:
screening according to the model state information to obtain production metadata containing model data;
and generating baseline data according to the production metadata containing the model data.
In an exemplary embodiment of the present disclosure, the metadata information further includes model naming information of the metadata;
the generating baseline data from the production metadata includes:
screening according to the model naming information to obtain production metadata with model names conforming to preset naming rules;
and generating baseline data according to the production metadata of which the model names accord with preset naming rules.
In an exemplary embodiment of the disclosure, the comparing the metadata with the baseline data to obtain difference contrast information includes:
obtaining model information, index information, field information and/or interface information of the metadata;
comparing the model information with the baseline data to obtain model difference information;
comparing the index information with the baseline data to obtain index difference information;
comparing the field information with the baseline data to obtain field difference information;
comparing the interface information with the baseline data to obtain interface difference information;
difference contrast information associated with the model difference information, index difference information field difference information, and/or interface difference information is generated.
In one exemplary embodiment of the present disclosure, the management pre-warning information includes pre-warning content and/or pre-warning level associated with the difference contrast information.
In an exemplary embodiment of the present disclosure, after generating the management pre-warning information according to the difference comparison information, the method further includes:
and updating the baseline data according to the management early warning information.
According to an aspect of the present disclosure, there is provided a metadata management apparatus characterized by comprising:
the system comprises a baseline generation unit, a service system and a service system, wherein the baseline generation unit is configured to acquire metadata information in the service system and generate baseline data according to the metadata information;
the difference comparison unit is configured to extract metadata from the service system and compare the metadata with the baseline data to obtain difference comparison information;
and the early warning generation unit is configured to generate management early warning information according to the difference comparison information.
According to one aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program, characterized in that the computer program, when executed by a processor, implements any of the above-described metadata management methods.
According to one aspect of the present disclosure, there is provided an electronic device, characterized by comprising a processor and a memory; wherein the memory is for storing executable instructions of the processor, the processor being configured to perform any of the metadata management methods described above via execution of the executable instructions.
In the metadata management method provided by the exemplary embodiment of the present disclosure, by combing the metadata information of the service system, a baseline data version is generated and managed, so that the system is prevented from being bloated. The method can check the metadata of the business system by taking the newly released baseline data as a reference, and timely find out problems and early warning. The metadata early warning monitoring platform formed based on the method can visually see the current situation of system metadata, so that metadata monitoring management is manually changed into a systematic and automatic direction.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
Fig. 1 schematically illustrates a flowchart of steps of a metadata management method in an exemplary embodiment of the present disclosure.
Fig. 2 schematically illustrates a partial step flow diagram of a metadata management method in an exemplary embodiment of the present disclosure.
Fig. 3 schematically illustrates a partial step flow diagram of a metadata management method in an exemplary embodiment of the present disclosure.
Fig. 4 schematically illustrates a partial step flow diagram of a metadata management method in an exemplary embodiment of the present disclosure.
Fig. 5 schematically illustrates a partial step flow diagram of a metadata management method in an exemplary embodiment of the present disclosure.
Fig. 6 schematically illustrates a management platform architecture block diagram of a metadata management method in an application scenario in an exemplary embodiment of the present disclosure.
Fig. 7 schematically illustrates a block diagram of a metadata management apparatus in an exemplary embodiment of the present disclosure.
Fig. 8 schematically illustrates a schematic diagram of a program product in an exemplary embodiment of the present disclosure.
Fig. 9 schematically illustrates a block diagram of an electronic device in an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
At present, the development and maintenance of many database systems are two independent processes, and models and codes developed by developers cannot be effectively notified to database maintainers, so that metadata problems, system problems, interface faults and the like occur in many cases, and the metadata problems are discovered and processed afterwards. This passive approach is generally ineffective. In addition, metadata is managed and controlled by a reinforced management means, so that a plurality of human factors are increased in the operation process, and the maintenance cost and the risk are improved.
In combination with the above, such metadata management is not an optimal approach. The main reasons are:
1) Most business systems are not fully considered at the beginning of system design, and metadata monitoring and management problems after operation are not fully considered, so that the management has great artificial randomness.
2) The manual management mode can not early warn in time, and the occurrence of system problems is avoided.
3) The more and more systems and the higher and higher complexity, the system is bulky and difficult to manage.
4) The manual operation steps are more, and the operation and maintenance cost is increased.
5) The manager has no visual perception of the current status of the system metadata.
Based on the above problem analysis, the present disclosure provides a metadata management method, a metadata management apparatus, a computer-readable storage medium, and an electronic device. The following describes embodiments of the present disclosure in detail with reference to specific examples.
In an exemplary embodiment of the present disclosure, there is provided a metadata management method, as shown in fig. 1, which may mainly include the steps of:
s110, acquiring metadata information in a service system, and generating baseline data according to the metadata information.
Aiming at a service system needing to be monitored and managed, the method comprises the steps of firstly acquiring metadata information in the service system, and then generating baseline data of the service system according to the metadata information. Metadata is data describing other data, or structural data for providing information about a certain resource. Metadata information may be used to describe data attributes to support functions such as indicating storage locations, historical data, resource lookups, file records, and the like. The baseline data may be stored in a database for reflecting metadata information in the business system at the current time.
And S120, collecting metadata from the service system, and comparing the metadata with the baseline data to obtain difference comparison information.
Business systems are typically in iterative development mode, and as business systems operate, the metadata and data involved therein also change continuously. The step collects the metadata of the latest state from the service system, and then the collected metadata can be also stored in a database to be compared with the baseline data in the database so as to obtain difference comparison information. The difference comparison information may reflect the difference between the metadata in the latest business system and the previously generated baseline data, and may be embodied in one or more data dimensions such as a model, an index, a field, an interface, etc. The actions of collecting metadata and comparing to obtain the difference comparison information in this step may be performed under the triggering of a task instruction, or may be performed automatically on a preset time node, or may be performed continuously and automatically with a preset time period as a time interval, which is not particularly limited in this exemplary embodiment.
And S130, generating management early warning information according to the difference comparison information.
According to the difference comparison information obtained in step S120, the present step may generate management early-warning information corresponding to the difference comparison information, where the management early-warning information may include early-warning content and/or early-warning level associated with the difference comparison information. The early warning content may include specific difference comparison results, such as increase or decrease of a model, increase or decrease of an index, and the like. The early warning level can be preset into a plurality of levels according to the type of the difference comparison result and the difference size, for example, the early warning level can be divided into red early warning, yellow early warning and green early warning according to the emergency degree of early warning. The green early warning represents that metadata is abnormal, but the usage of a service system is not affected. Yellow early warning represents that metadata is abnormal, and service system performance can be affected to a certain extent. The red early warning represents that metadata is abnormal, and service system faults can be caused. The management early warning information generated in the step can be sent to related service managers, and the service managers adjust metadata in the service system according to the management early warning information so as to improve the service performance of the service system. The management early warning information can be sent by adopting a real-time information transmission mode such as mail, short message and the like, and can be intuitively displayed on a corresponding monitoring management system or platform by adopting a mode of generating a visual chart. In addition, in the present exemplary embodiment, the baseline data generated in step S110 may also be updated with the management early-warning information. And when the metadata collected in the service system is monitored and managed later, the updated baseline data is used as a basis for difference comparison.
In the metadata management method provided in the present exemplary embodiment, by combing service system metadata information, a baseline data version is generated and managed, and system bloat is avoided. The method can check the metadata of the business system by taking the newly released baseline data as a reference, and timely find out problems and early warning. The metadata early warning monitoring platform formed based on the method can visually see the current situation of system metadata, so that metadata monitoring management is manually changed into a systematic and automatic direction.
In another exemplary embodiment of the present disclosure, the metadata information acquired in step S110 may include usage status information of metadata. Meanwhile, as shown in fig. 2, generating baseline data from metadata information in a database in step S110 may include the steps of:
and S210, screening to obtain the metadata in use according to the use state information of the metadata.
This step may determine whether metadata is being used or not based on usage status information of the metadata, for example, may determine whether a data pattern (schema) in a business system is being used or not.
And S220, taking the metadata in use as production metadata, and generating baseline data according to the production metadata.
For metadata in use, it may be used as production metadata, and for unused metadata, it may be used as non-production metadata. This step will clean up and remove non-production metadata, and then generate baseline data from the production metadata.
The metadata information acquired in step S110 may further include model state information of the metadata on the basis of the above exemplary embodiment. As shown in fig. 3, generating baseline data from production metadata in step S220 may include:
and S310, screening according to the model state information to obtain production metadata containing the model data.
The step can judge whether the production metadata contains model data or not according to the model state information, namely judge whether the model data is empty or not, so that the production metadata containing the model data can be screened.
And S320, generating baseline data according to the production metadata containing the model data.
According to the determination result in step S310, after the production metadata in which the model data is empty is cleared, the present step may generate baseline data from the production metadata including the model data.
In another exemplary embodiment of the present disclosure, the metadata information acquired in step S110 may further include model naming information of the metadata; as shown in fig. 4, generating baseline data from production metadata in step S220 may include:
and S410, screening according to the model naming information to obtain production metadata with the model names conforming to preset naming rules.
According to the method, whether the model name of the metadata accords with the preset naming rule can be judged according to the model naming information of the metadata, so that production metadata with the model name which accords with the preset naming rule can be obtained through screening.
And S420, generating baseline data according to production metadata with model names conforming to preset naming rules.
According to the determination result in step S410, after removing the production metadata with irregular model names, the step may generate baseline data according to the production metadata with model names more conforming to the preset naming rule.
In addition, the metadata access frequency script can be deployed, and if the production metadata is not accessed, the metadata is judged to be removed according to the running result of the metadata access frequency script.
As shown in fig. 5, in another exemplary embodiment of the present disclosure, comparing the metadata with the baseline data in step S120 to obtain difference contrast information may include the following steps:
s510, obtaining model information, index information, field information and/or interface information of the metadata.
The step can firstly acquire the related information of the metadata in one or more dimensions such as a model, an index, a field, an interface and the like, and can also acquire various different difference information in the subsequent comparison process.
And S520, comparing the model information with the baseline data to obtain model difference information.
For the model information, model difference information can be obtained after comparison with the baseline data, and for example, model addition, model reduction and the like can be included.
And S530, comparing the index information with the baseline data to obtain index difference information.
For the index information, index difference information can be obtained after comparison with the baseline data, and for example, index addition, index reduction, index modification and the like can be included.
S540, comparing the field information with the baseline data to obtain field difference information.
For field information, field difference information can be obtained after comparison with baseline data, and can include field addition, field reduction, field modification, and the like.
S550, comparing the interface information with the baseline data to obtain interface difference information.
For the interface information, the interface difference information can be obtained after the baseline data is compared, and for example, the interface difference information can comprise the addition of an interface field, the reduction of an interface field, the modification of an interface field and the like.
And S560, generating difference comparison information associated with the model difference information, the index difference information field difference information and/or the interface difference information.
After the difference comparison in the above steps is performed to obtain the relevant difference information, the present step may generate difference comparison information associated with the above difference information, that is, difference comparison information associated with model difference information, index difference information field difference information, and/or interface difference information. The difference comparison information of various types and dimensions can provide different management basis in the process of monitoring the metadata.
It should be noted that while the above exemplary embodiments describe the steps of the methods in this disclosure in a particular order, this does not require or imply that the steps must be performed in that particular order or that all of the steps must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
The metadata management method in the above exemplary embodiments is described in detail below in connection with a specific application scenario.
As shown in fig. 6, the metadata management method related in the present disclosure may be integrated in a metadata monitoring management platform, where the monitoring management function of the platform is mainly embodied in the following aspects:
1. metadata baseline version management:
this stage is used for rejecting non-production metadata, carding out production metadata, and then generating baseline data for management, and the specific steps may include:
1) Metadata information of the system is extracted.
2) Checking and confirming whether the system Schema is in production use or not, and rejecting non-production schemas.
3) And checking whether the model data is empty, and rejecting the empty data model.
4) And checking naming rules, and eliminating the irregular model.
5) Deploying metadata access frequency scripts, and eliminating if the metadata system is not accessed.
6) And confirming the metadata of the combing completion.
7) After the confirmation is completed, the non-production metadata is cleaned up.
8) Baseline data is generated.
2. Auditing metadata:
the stage is used for carrying out model checking, field checking, interface checking and index checking on the extracted metadata based on the baseline data. The specific steps may include:
1) The latest metadata of the system is extracted through an open source ETL (extraction, conversion, loading tool).
2) And performing difference comparison on the latest metadata of the extraction system and the baseline data through open source ETL scheduling model checking, field checking, interface checking and index checking programs, and then generating data to an application layer.
3. Metadata hierarchical early warning:
the stage is used for dividing red, yellow and green early warning levels according to the severity level of the audit and sending warning mails. The specific steps may include:
1) The early warning level, the early warning type, the early warning rule and the early warning content are set as shown in table 1.
2) And carrying out mail notification on the early warning information of the red and yellow levels according to the matching of the generated audit data and the early warning level.
Table 1 management Pre-alarm information example
Figure BDA0001869188700000101
Figure BDA0001869188700000111
4. Metadata management monitoring:
the stage is used for displaying the metadata checking condition and the metadata grading early warning details of each system through a visual chart in a webpage according to the application data generated by the database. The specific steps may include:
1) The metadata status of one system is displayed, and different system metadata can be checked by scrolling left and right.
2) Model growth trend, model consistency monitoring, index consistency monitoring, field consistency monitoring, interface field consistency monitoring and field relation monitoring are shown in a chart mode.
3) The number of the red, yellow and green early warning strips and the grading early warning details of the early warning monitoring platform are displayed, and the page viewing can be realized.
5. Baseline management maintenance:
the stage is used for maintaining and managing the metadata baseline according to the content of the metadata early warning monitoring platform. The specific steps may include:
1) Confirming and processing the early warning event according to the content of the early warning monitoring platform;
2) After the treatment is completed, the baseline data is subjected to differential restoration.
Based on the above application scenario, the disclosure formulates a set of management mechanism, which is changed from passive management to active management. The current situation of system metadata can be visually seen through the metadata early warning monitoring platform, so that metadata monitoring management is changed from a manual mode to a systematic and automatic mode.
In an exemplary embodiment of the present disclosure, there is also provided a metadata management apparatus. As shown in fig. 7, the metadata management apparatus 700 may mainly include: a baseline generation unit 710, a difference comparison unit 720, and an early warning generation unit 730. Wherein the baseline generation unit 710 is configured to obtain metadata information in the database and generate baseline data according to the metadata information; the difference comparing unit 720 is configured to extract metadata from the database and compare the metadata with the baseline data to obtain difference comparison information; the early warning generation unit 730 is configured to generate management early warning information according to the difference contrast information.
The specific details of the above metadata management apparatus have been described in detail in the corresponding metadata management method, and thus are not described here again.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, can implement the above-described metadata management method of the present disclosure. In some possible implementations, aspects of the disclosure may also be implemented in the form of a program product including program code; the program product may be stored on a non-volatile storage medium (which may be a CD-ROM, a U-disk or a removable hard disk, etc.) or on a network; when the program product is run on a computing device (which may be a personal computer, a server, a terminal device or a network device, etc.), the program code is for causing the computing device to carry out the method steps in the above-mentioned exemplary embodiments of the present disclosure.
Referring to fig. 8, a program product 800 for implementing the above-described methods according to embodiments of the present disclosure may employ a portable compact disk read-only memory (CD-ROM) and include program code and may run on a computing device (e.g., a personal computer, a server, a terminal device, or a network device, etc.). However, the program product of the present disclosure is not limited thereto. In the present exemplary embodiment, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may take the form of any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium.
The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, 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 of the foregoing.
The readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the C programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In cases involving remote computing devices, the remote computing devices may be connected to the user computing devices through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), etc.; alternatively, it may be connected to an external computing device, for example, using an Internet service provider to connect through the Internet.
In an exemplary embodiment of the present disclosure, there is also provided an electronic device including at least one processor and at least one memory for storing executable instructions of the processor; wherein the processor is configured to perform the method steps in the above-described exemplary embodiments of the present disclosure via execution of the executable instructions.
An electronic device 900 in the present exemplary embodiment is described below with reference to fig. 9. The electronic device 900 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present disclosure in any way.
Referring to fig. 9, the electronic device 900 is embodied in the form of a general purpose computing device. Components of electronic device 900 may include, but are not limited to: at least one processing unit 910, at least one storage unit 920, a bus 930 connecting the different system components (including the processing unit 910 and the storage unit 920), a display unit 940.
Wherein the storage unit 920 stores program code executable by the processing unit 910 such that the processing unit 910 performs the method steps in the above-described exemplary embodiments of the present disclosure.
The storage unit 920 may include readable media in the form of volatile storage units, such as random access memory unit 921 (RAM) and/or cache memory unit 922, and may further include read only memory unit 923 (ROM).
The storage unit 920 may also include a program/utility 924 having a set (at least one) of program modules 925, including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The bus 930 may be one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 900 may also communicate with one or more external devices 1000 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that allow a user to interact with the electronic device 900, and/or any device (e.g., router, modem, etc.) that allows the electronic device 900 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 950. Also, electronic device 900 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 960. As shown in fig. 9, the network adapter 960 may communicate with other modules of the electronic device 900 via the bus 930. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 900, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
The above described features, structures or characteristics may be combined in any suitable manner in one or more embodiments, such as the possible, interchangeable features as discussed in connection with the various embodiments. In the above description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. One skilled in the relevant art will recognize, however, that the disclosed aspects may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

Claims (9)

1. A metadata management method, comprising:
acquiring metadata information in a service system, screening according to the metadata information to obtain production metadata, and generating baseline data according to the production metadata; the metadata information comprises using state information of metadata, model state information of the metadata and model naming information of the metadata;
collecting metadata from the service system, and comparing the metadata with the baseline data to obtain difference comparison information; the acquisition metadata comprises model information, index information, field information and/or interface information of the metadata;
generating management early warning information according to the difference comparison information; the difference contrast information includes: model difference information, index difference information, field difference information and/or interface difference information-associated difference comparison information;
and updating the baseline data according to the management early warning information.
2. The metadata management method according to claim 1, wherein the metadata information includes usage status information of the metadata;
the generating baseline data according to the metadata information comprises the following steps:
screening to obtain the metadata in use according to the use state information of the metadata;
and taking the metadata in use as production metadata, and generating baseline data according to the production metadata.
3. The metadata management method according to claim 2, wherein the metadata information further includes model state information of the metadata;
the generating baseline data from the production metadata includes:
screening according to the model state information to obtain production metadata containing model data;
and generating baseline data according to the production metadata containing the model data.
4. The metadata management method according to claim 2, wherein the metadata information further includes model naming information of the metadata;
the generating baseline data from the production metadata includes:
screening according to the model naming information to obtain production metadata with model names conforming to preset naming rules;
and generating baseline data according to the production metadata of which the model names accord with preset naming rules.
5. The method of claim 1, wherein comparing the metadata with the baseline data to obtain difference comparison information comprises:
obtaining model information, index information, field information and/or interface information of the metadata;
comparing the model information with the baseline data to obtain model difference information;
comparing the index information with the baseline data to obtain index difference information;
comparing the field information with the baseline data to obtain field difference information;
comparing the interface information with the baseline data to obtain interface difference information;
difference contrast information associated with the model difference information, index difference information field difference information, and/or interface difference information is generated.
6. The metadata management method according to claim 1, wherein the management pre-warning information includes pre-warning content and/or pre-warning level associated with the difference contrast information.
7. A metadata management apparatus, comprising:
the base line generation unit is configured to acquire metadata information in the service system, screen production metadata according to the metadata information, and generate base line data according to the production metadata; the metadata information comprises using state information of metadata, model state information of the metadata and model naming information of the metadata;
the difference comparison unit is configured to extract metadata from the service system and compare the metadata with the baseline data to obtain difference comparison information; collecting metadata including model information, index information, field information and/or interface information of the metadata;
the early warning generation unit is configured to generate management early warning information according to the difference comparison information; the difference contrast information includes: model difference information, index difference information, field difference information and/or interface difference information-associated difference comparison information;
the device is also used for updating the baseline data according to the management early warning information.
8. A computer readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the metadata management method of any of claims 1-6.
9. An electronic device, comprising:
a processor;
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the metadata management method of any of claims 1-6 via execution of the executable instructions.
CN201811368352.7A 2018-11-16 2018-11-16 Metadata management method and device, storage medium and electronic equipment Active CN111198902B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811368352.7A CN111198902B (en) 2018-11-16 2018-11-16 Metadata management method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811368352.7A CN111198902B (en) 2018-11-16 2018-11-16 Metadata management method and device, storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN111198902A CN111198902A (en) 2020-05-26
CN111198902B true CN111198902B (en) 2023-06-16

Family

ID=70743678

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811368352.7A Active CN111198902B (en) 2018-11-16 2018-11-16 Metadata management method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN111198902B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112783931A (en) * 2020-07-21 2021-05-11 南方电网调峰调频发电有限公司信息通信分公司 System and method for realizing data sharing service based on multi-view data directory
CN112597207B (en) * 2020-12-29 2022-09-23 科技谷(厦门)信息技术有限公司 Metadata management system
CN113392076A (en) * 2021-07-08 2021-09-14 网银在线(北京)科技有限公司 Method, device, electronic equipment and medium for acquiring metadata quality information

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013011389A1 (en) * 2011-07-15 2013-01-24 International Business Machines Corporation Versioning of metadata, including presentation of provenance and lineage for versioned metadata
CN103473672A (en) * 2013-09-30 2013-12-25 国家电网公司 System, method and platform for auditing metadata quality of enterprise-level data center
CN106708657A (en) * 2015-08-03 2017-05-24 中兴通讯股份有限公司 Metadata management method and apparatus, and distributed file system
CN108572996A (en) * 2017-03-14 2018-09-25 北京京东尚科信息技术有限公司 Synchronous method, device, electronic equipment and the storage medium of database table structure

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102081620A (en) * 2009-11-26 2011-06-01 中国移动通信集团贵州有限公司 Method and device for controlling database object change
CN102054041B (en) * 2010-12-30 2013-06-12 用友软件股份有限公司 Method and system for upgrading metadata
CN102289460B (en) * 2011-07-13 2013-03-27 中国工商银行股份有限公司 Method and system for performing report metadata synchronization on testing environments
CN102929878B (en) * 2011-08-09 2016-09-07 阿里巴巴集团控股有限公司 A kind of databases comparison management method and device
US10291506B2 (en) * 2015-03-04 2019-05-14 Fisher-Rosemount Systems, Inc. Anomaly detection in industrial communications networks
CN108304413A (en) * 2017-01-13 2018-07-20 北京京东尚科信息技术有限公司 distributed data warehouse monitoring method, device, electronic equipment and storage medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013011389A1 (en) * 2011-07-15 2013-01-24 International Business Machines Corporation Versioning of metadata, including presentation of provenance and lineage for versioned metadata
CN103473672A (en) * 2013-09-30 2013-12-25 国家电网公司 System, method and platform for auditing metadata quality of enterprise-level data center
CN106708657A (en) * 2015-08-03 2017-05-24 中兴通讯股份有限公司 Metadata management method and apparatus, and distributed file system
CN108572996A (en) * 2017-03-14 2018-09-25 北京京东尚科信息技术有限公司 Synchronous method, device, electronic equipment and the storage medium of database table structure

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Vassiliadis P.Arktos:To-wards modeling,design,control and execution of ETL Processes.《Information System》.2001,摘要. *
梁美红 ; 张男楠 ; 李建 ; 伍东 ; 胡永泉 ; 杨静 ; .一种钻井数据仓库ETL系统的设计.计算机技术与发展.2010,(03),全文. *

Also Published As

Publication number Publication date
CN111198902A (en) 2020-05-26

Similar Documents

Publication Publication Date Title
CN111198902B (en) Metadata management method and device, storage medium and electronic equipment
US10970095B2 (en) Obtaining insights from a distributed system for a dynamic, customized, context-sensitive help system
CN111294217B (en) Alarm analysis method, device, system and storage medium
US20140075357A1 (en) Enabling real-time opertional environment conformity to an enterprise model
WO2020154604A1 (en) Systems and methods for automating and monitoring software development operations
US20080114878A1 (en) Monitoring and management of assets, applications, and services using aggregated event and performance data thereof
US8112657B2 (en) Method, computer, and computer program product for hardware mapping
CN103038752A (en) Bug clearing house
JP5532053B2 (en) Operation management apparatus and operation management method
CN113396395A (en) Method for effectively evaluating log mode
EP2415209A1 (en) Network analysis system
US10372572B1 (en) Prediction model testing framework
CN108959101A (en) Test result processing method, device, equipment and memory software testing system
CN114020581A (en) Alarm correlation method based on topological optimization FP-Growth algorithm
CN108920322A (en) A kind of method, apparatus and computer storage medium of middleware operational monitoring
CN109240916A (en) Information output controlling method, device and computer readable storage medium
CN102077510A (en) Targeted user notification of messages in a monitoring system
CN111597091A (en) Data monitoring method and system, electronic equipment and computer storage medium
US11838171B2 (en) Proactive network application problem log analyzer
US11966884B2 (en) Using distributed databases for network regression analysis
CN116450464A (en) Operation and maintenance management method, system and equipment
CN103455864A (en) Integrated operation and maintenance management platform based on uniform configuration library and knowledge base
CN115422202A (en) Service model generation method, service data query method, device and equipment
CN112131090B (en) Service system performance monitoring method, device, equipment and medium
CN116136801A (en) Cloud platform data processing method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant