CN117707886A

CN117707886A - Metadata acquisition method and device

Info

Publication number: CN117707886A
Application number: CN202311654560.4A
Authority: CN
Inventors: 陈浩亮; 张静芳
Original assignee: Clp Jinxin Software Shanghai Co ltd
Current assignee: Clp Jinxin Software Shanghai Co ltd
Priority date: 2023-12-04
Filing date: 2023-12-04
Publication date: 2024-03-15

Abstract

The application provides a metadata acquisition method and device, which respond to monitoring task creation operation applied in a task management interface and display a task creation interface in a graphical user interface; the task creation interface is displayed with a monitoring task configuration item; responding to a monitoring task configuration operation aiming at a monitoring task configuration item, and creating a metadata acquisition task for monitoring a target database by setting a data monitoring node and a data acquisition strategy; and executing a metadata acquisition task according to the data acquisition strategy, and acquiring the corresponding node acquisition data of the target database on each data monitoring node to obtain the target metadata of the target database. Therefore, the acquisition difficulty of the target metadata is simplified, the important metadata of the target database can be acquired in a targeted manner, and the acquisition efficiency of the metadata is accelerated.

Description

Metadata acquisition method and device

Technical Field

The present disclosure relates to the field of data monitoring technologies, and in particular, to a metadata collection method and apparatus.

Background

Metadata (Metadata), also called intermediate data and relay data, is data (data about data) describing data, mainly describing data attribute (property) information, and is used to support functions such as indicating storage location, history data, resource searching, file recording, and the like. Metadata is an electronic catalog, and in order to achieve the purpose of cataloging, the contents or characteristics of data must be described and collected, so as to achieve the purpose of assisting in data retrieval.

At present, the metadata acquisition process is not perfect and transparent enough, metadata administrators cannot acquire required metadata in a targeted manner in the metadata acquisition process, and cannot monitor the metadata acquisition process in real time, so that the metadata acquisition process is complex and the acquisition efficiency is low.

Disclosure of Invention

In view of this, an object of the present application is to provide a metadata collection method and apparatus, which can obtain important metadata of a target database in a targeted manner by setting a data monitoring node, so as to improve metadata collection efficiency and reduce complexity of metadata collection.

The embodiment of the application provides a metadata acquisition method, which comprises the steps of providing a graphical user interface through terminal equipment, wherein a task management interface is displayed in the graphical user interface; the metadata acquisition method comprises the following steps:

displaying a task creation interface in the graphical user interface in response to the monitor task creation operation applied in the task management interface; the task creation interface is used for displaying a monitoring task configuration item;

responding to the monitoring task configuration operation aiming at the monitoring task configuration item, and creating a metadata acquisition task for monitoring the target database by setting a data monitoring node and a data acquisition strategy;

And executing the metadata acquisition task according to the data acquisition strategy, and acquiring node acquisition data corresponding to each data monitoring node of the target database to obtain target metadata of the target database.

In a possible implementation manner, a task monitoring list is displayed in the task management interface, wherein the task monitoring list comprises created metadata acquisition tasks; the metadata acquisition method further comprises the following steps:

responding to task viewing operation aiming at the metadata acquisition task, and displaying a task monitoring interface in the graphical user interface; the task monitoring interface comprises a flow display area; the flow display area displays the task execution flow of the metadata acquisition task; the task execution flow comprises the data monitoring nodes related to the metadata acquisition task and the acquisition sequence circulation direction among the data monitoring nodes.

In one possible embodiment, the metadata collection method further includes:

and responding to the node selection operation of the target data monitoring node in the task execution flow, and displaying node detail information of the target data monitoring node nearby the target data monitoring node.

In one possible implementation manner, a small map of the task execution flow is displayed in the task monitoring interface; the metadata acquisition method further comprises the following steps:

and adjusting the display position of the task execution flow in the flow display area in response to a display adjustment operation applied in the minimap.

In one possible embodiment, the metadata collection method further includes:

aiming at each data monitoring node, acquiring a metadata acquisition log of the data monitoring node;

and determining the metadata acquisition state of the data monitoring node by analyzing the metadata acquisition log, and displaying a state prompt identifier corresponding to the metadata acquisition state around the data monitoring node.

In one possible embodiment, the metadata collection method further includes:

determining whether to publish the target metadata to a target data system by comparing the target metadata with historical metadata of the target database;

if yes, the target metadata is issued to the target data system, and metadata change information is recorded.

In one possible embodiment, the data acquisition strategy includes acquisition time and acquisition requirements of each data monitoring node; and executing the metadata acquisition task according to the data acquisition strategy, acquiring node acquisition data corresponding to each data monitoring node of the target database, and obtaining target metadata of the target database, wherein the metadata acquisition task comprises the following steps:

For each data monitoring node, responding to the acquisition time reaching the data monitoring node, and acquiring node acquisition data of the target database according to the acquisition requirement of the data monitoring node;

until metadata collection is completed at each data monitoring node, determining target metadata of the target database based on the node collection data acquired at each data monitoring node.

In one possible implementation, the graphical user interface has a system creation interface displayed therein; the metadata acquisition method further comprises the following steps:

and responding to the system creation operation applied in the system creation interface, and completing the creation of the newly added service system by configuring the system category and the system attribute information under the system category.

In one possible implementation, the graphical user interface has a data source configuration interface displayed therein; the metadata acquisition method further comprises the following steps:

and responding to the data source association operation applied in the data source configuration interface, and determining a system database called by the newly added service system when the service is transacted by configuring database attribute information.

The embodiment of the application also provides a metadata acquisition device, wherein a graphical user interface is provided through the terminal equipment, and a task management interface is displayed in the graphical user interface; the metadata acquisition device includes:

An interface display module for displaying a task creation interface in the graphical user interface in response to the monitoring task creation operation applied in the task management interface; the task creation interface is used for displaying a monitoring task configuration item;

the task configuration module is used for responding to the monitoring task configuration operation aiming at the monitoring task configuration item, and creating a metadata acquisition task for monitoring the target database by setting a data monitoring node and a data acquisition strategy;

and the data acquisition module is used for executing the metadata acquisition task according to the data acquisition strategy, and acquiring node acquisition data corresponding to each data monitoring node of the target database so as to obtain target metadata of the target database.

In a possible implementation manner, a task monitoring list is displayed in the task management interface, wherein the task monitoring list comprises created metadata acquisition tasks; the metadata acquisition device is also used for:

In a possible embodiment, the metadata acquisition device is further configured to:

In one possible implementation manner, a small map of the task execution flow is displayed in the task monitoring interface; the metadata acquisition device is also used for:

In one possible embodiment, the data acquisition strategy includes acquisition time and acquisition requirements of each data monitoring node; the data acquisition module is used for executing the metadata acquisition task according to the data acquisition strategy, acquiring node acquisition data corresponding to each data monitoring node of the target database, and when obtaining target metadata of the target database, the data acquisition module is used for:

In one possible implementation, the graphical user interface has a system creation interface displayed therein; the metadata acquisition device is also used for:

In one possible implementation, the graphical user interface has a data source configuration interface displayed therein; the metadata acquisition device is also used for:

The embodiment of the application also provides electronic equipment, which comprises: the system comprises a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, when the electronic device is running, the processor communicates with the memory through the bus, and the machine-readable instructions are executed by the processor to perform the steps of the metadata acquisition method.

Embodiments of the present application also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of a metadata collection method as described above.

According to the metadata acquisition method and device provided by the embodiment of the application, a task creation interface is displayed in a graphical user interface in response to monitoring task creation operation applied in a task management interface; the task creation interface is displayed with a monitoring task configuration item; responding to a monitoring task configuration operation aiming at a monitoring task configuration item, and creating a metadata acquisition task for monitoring a target database by setting a data monitoring node and a data acquisition strategy; and executing a metadata acquisition task according to the data acquisition strategy, and acquiring the corresponding node acquisition data of the target database on each data monitoring node to obtain the target metadata of the target database. Therefore, a metadata manager can customize and acquire the expected target metadata related to the target database by creating metadata acquisition tasks according to requirements, so that acquisition difficulty of the target metadata is simplified, important metadata of the target database can be acquired in a targeted manner, and acquisition efficiency of the metadata is accelerated.

In order to make the above objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered limiting the scope, and that other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flowchart of a metadata collection method provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of a task creation interface according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a task monitoring list according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a task monitoring interface according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a system creation interface according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a data source association interface according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a metadata collection device according to an embodiment of the present application;

Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, 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, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. Based on the embodiments of the present application, every other embodiment that a person skilled in the art would obtain without making any inventive effort is within the scope of protection of the present application.

According to research, at present, the metadata acquisition process is not perfect and transparent, metadata administrators cannot acquire required metadata in a targeted manner in the metadata acquisition process, and cannot monitor the metadata acquisition process in real time, so that the metadata acquisition process is complex and the acquisition efficiency is low.

Based on this, the embodiment of the application provides a metadata collection method, and a metadata manager can customize and obtain the target metadata about the target database by creating metadata collection tasks according to requirements, so that the collection difficulty of the target metadata is simplified, the important metadata of the target database can be collected in a targeted manner, and the metadata collection efficiency is accelerated.

Referring to fig. 1, fig. 1 is a flowchart of a metadata collection method according to an embodiment of the present application. Providing a graphical user interface through terminal equipment, wherein a task management interface is displayed in the graphical user interface; as shown in fig. 1, a metadata collection method provided in an embodiment of the present application includes:

s101, responding to the monitoring task creation operation applied in the task management interface, and displaying a task creation interface in the graphical user interface; and the task creation interface is displayed with a monitoring task configuration item.

S102, responding to the monitoring task configuration operation aiming at the monitoring task configuration item, and creating a metadata acquisition task for monitoring the target database by setting a data monitoring node and a data acquisition strategy.

And S103, executing the metadata acquisition task according to the data acquisition strategy, and acquiring node acquisition data corresponding to each data monitoring node of the target database so as to obtain target metadata of the target database.

According to the metadata acquisition method provided by the embodiment of the application, the task management interface can be displayed in the graphical user interface of the terminal equipment used by the metadata manager, and the metadata manager can automatically create a metadata acquisition task for acquiring target metadata related to the target database by means of monitoring task creation operation; responsive to a monitoring task creation operation by the metadata administrator, displaying a task creation interface in the graphical user interface; setting a data monitoring node and a data acquisition strategy by applying a monitoring task configuration operation in a task creation interface so as to create and obtain a metadata acquisition task for monitoring a target database, so that a metadata manager can set a corresponding metadata acquisition task according to actual metadata acquisition requirements; and according to the set data acquisition strategy, acquiring target metadata of a target database expected by a metadata manager by executing a metadata acquisition task. Therefore, the acquisition difficulty of the target metadata can be simplified, the important metadata of the target database can be acquired in a targeted manner, and the acquisition efficiency of the metadata is accelerated.

In step S101, a task management interface is displayed in a graphical user interface of a terminal device used by a metadata administrator, and the metadata administrator can trigger entering a task creation interface by applying a monitoring task creation operation in the task management interface so as to complete configuration of metadata acquisition tasks in the task creation interface; specifically, a task creation interface is triggered to be displayed in a graphical user interface in response to a monitoring task creation operation applied by a metadata administrator in a task management interface; the task creation interface may be displayed in a superimposed manner on the task management interface, and may also be displayed in a graphical user interface in a page skip or switch manner.

In the scheme provided by the application, the monitoring task creation operation can be triggered by clicking a control corresponding to the monitoring task creation operation; specifically, a control corresponding to the creation operation of the monitoring task can be clicked by a finger, a mouse, a preset combination key and the like; the control corresponding to the operation of the monitoring task creation can be clicked through keys such as an L1 key, an R1 key, a ctrl key, an alt key, an a key and the like in the handle, and preset keys can be set manually according to requirements; or clicking a control corresponding to the monitoring task creation operation in a mode of sound control and preset trigger action.

Here, the task creation interface displays monitoring task configuration items, and the metadata administrator can create and obtain a metadata acquisition task for monitoring target metadata of the target database by completing configuration of each monitoring task configuration item.

In step S102, the metadata administrator may complete the configuration of the metadata collection task by configuring the monitoring task configuration item in the task creation interface; specifically, in response to a monitoring task configuration operation applied by a metadata administrator to each monitoring task configuration item in a task creation interface, a metadata acquisition task for monitoring a target database is created by setting a data monitoring node and a data acquisition strategy related to the metadata acquisition task.

The data monitoring node may be considered as a sub-acquisition task included in the metadata acquisition task, and may include preparation of basic data, construction of a temporary table for metadata acquisition, construction of a deduplication table for removing duplicate metadata, updating of metadata in a draft table, comparison of metadata recorded in the draft table and a formal table, automatic publishing of metadata, storing of metadata into the formal table, discarding of acquisition registration information according to a data source id, pushing of an ES search engine, storing of the acquisition registration table, deletion of the temporary table, buffering of the table, success/failure of acquisition, and the like.

In the scheme provided by the application, the monitoring task configuration operation can be triggered by clicking the monitoring task configuration item; specifically, the monitoring task configuration item can be clicked by a finger, a mouse, a preset combination key and the like; the monitoring task configuration item can be clicked through keys such as an L1 key, an R1 key, a ctrl key, an alt key, an a key and the like in the handle, and preset keys can be set manually according to requirements; or, the monitoring task configuration item can be clicked by means of sound control and preset triggering actions.

Referring to fig. 2, fig. 2 is a schematic diagram of a task creation interface according to an embodiment of the present application. As shown in fig. 2, a task creation interface 2b is displayed in the graphical user interface 2a, a monitoring task configuration item 2c is displayed in the task creation interface 2b, and a metadata administrator can create and obtain a metadata acquisition task by configuring the monitoring task configuration item 2 c.

After the metadata collection task is configured, the collection of the target metadata of the target database can be completed by executing the metadata collection task according to the data collection strategy.

In step S103, executing the created metadata acquisition task according to the data acquisition policy of the metadata acquisition task, and acquiring node acquisition data of the target database on each data monitoring node; and after the metadata acquisition task is completed, obtaining the target metadata of the target database.

Here, for each data monitoring node, there is a certain sequence in the acquisition sequence, and in order to ensure the continuity of the target metadata acquisition process, the acquisition of the target metadata of the target database can be completed one by one and continuously on each data detection node by configuring the acquisition time for each data monitoring node.

In one embodiment, the data acquisition strategy includes an acquisition time for each data monitoring node; step S103 includes:

s1031, for each data monitoring node, responding to the acquisition time reaching the data monitoring node, and acquiring the node acquisition data of the target database according to the acquisition requirement of the data monitoring node.

In the step, aiming at each data monitoring node in the metadata acquisition task, acquiring data of a node corresponding to a target database according to acquisition requirements on acquisition time of the data monitoring node; specifically, responding to the acquisition time reaching the data monitoring node, and acquiring node acquisition data related to a target database according to the acquisition requirement of the data monitoring node; thus, according to the acquisition time of each data monitoring node, the acquisition of the node acquisition data related to the target database is completed on each data monitoring node one by one.

S1032, determining the target metadata of the target database based on the node acquisition data acquired on each data monitoring node until the metadata acquisition is completed on each data monitoring node.

In the step, until the acquisition of metadata is completed on the data monitoring nodes included in the metadata acquisition task, the metadata acquisition task is determined to be completed, and at the moment, the node acquisition data acquired by the data monitoring nodes are synthesized, and the target metadata of the target database is acquired.

Here, in order to facilitate the metadata administrator to monitor the metadata collection progress in real time, the task execution flow of the metadata collection task may be displayed to the metadata administrator, so that the metadata administrator can check the completion condition of the metadata collection task on each data monitoring node in real time.

At this time, the metadata manager may trigger entering the task monitoring interface by selecting a metadata acquisition task desired to be checked in the task monitoring list, so as to check the completion progress of the selected metadata acquisition task in the task monitoring interface.

Here, the metadata manager may trigger the display of a task monitoring list in the task management interface and the inclusion of the created metadata collection task in the task monitoring list by selecting a task category.

Referring to fig. 3, fig. 3 is a schematic diagram of a task monitoring list according to an embodiment of the present application. As shown in fig. 3, the graphical user interface 3a displays a task classification area 3b and a list display area 3c, wherein the task classification area 3b displays a task category 3b-1; the task monitoring list 3c-1 is displayed in the list display area 3 c.

In one embodiment, a task monitoring list is displayed in the task management interface, wherein the task monitoring list comprises created metadata acquisition tasks; the metadata acquisition method further comprises the following steps:

and responding to the task viewing operation aiming at the metadata acquisition task, and displaying a task monitoring interface in the graphical user interface.

In the step, a metadata manager can select a metadata acquisition task expected to be monitored from the created metadata acquisition tasks through task checking operation, and the monitoring of the acquisition progress of the metadata acquisition task is completed in a task monitoring interface; specifically, a task checking operation of a metadata collection task which is established in a task monitoring list by a metadata manager is responded, a task monitoring interface is triggered to be displayed in a graphical user interface, and a task execution flow of the metadata collection task is displayed in the task monitoring interface, so that data monitoring nodes related to the metadata collection task, collection sequence circulation directions among all the data monitoring nodes, data collection progress of all the data monitoring nodes and the like are reflected through the task execution flow.

The task monitoring interface comprises a flow display area; the flow display area displays the task execution flow of the metadata acquisition task; the task execution flow comprises the data monitoring nodes related to the metadata acquisition task and the acquisition sequence circulation direction among the data monitoring nodes.

In the scheme provided by the application, the task viewing operation can be triggered by clicking the control corresponding to the task viewing operation; specifically, the control corresponding to the task viewing operation can be clicked through a finger, a mouse, a preset combination key and the like; the control corresponding to the task viewing operation can be clicked through keys such as an L1 key, an R1 key, a ctrl key, an alt key, an a key and the like in the handle, and preset keys can be set manually according to requirements; or clicking a control corresponding to the task viewing operation in a mode of sound control and preset triggering action.

Here, if the metadata administrator wants to view the node detail information of the data monitoring node in the task monitoring interface, the metadata administrator may trigger display of the node detail information of the selected target data monitoring node through a node selection operation.

In one embodiment, the metadata collection method further comprises:

In the step, the metadata manager can select a target data monitoring node from the data monitoring nodes in the task execution flow through node selection operation so as to trigger the display of node detail information of the target data monitoring node.

Specifically, in response to a node selection operation applied by a metadata administrator to a target data monitoring node in a task execution flow, triggering the display of node detail information of the target data monitoring node in the vicinity of the selected target data monitoring node; the node detail information comprises acquisition times, acquisition success times, acquisition failure times, acquisition start time, acquisition end time and the like.

Here, the selection of the target data monitoring node can be realized by clicking the operations such as the target data monitoring node; the selection of the target data monitoring node can be realized by hovering a touch cursor on the target data monitoring node, and the selection can be determined according to actual conditions without limitation.

Under the condition that metadata acquisition tasks are too complicated, namely under the condition that data monitoring nodes related to the metadata acquisition tasks are too many, all the data monitoring nodes cannot be displayed in a task monitoring interface completely, so that in order to enable each data monitoring node to be displayed to a metadata manager in the task monitoring interface, the metadata manager can adjust a task execution flow displayed in a flow display area through a small map by setting the small map.

In one embodiment, a small map of the task execution flow is displayed in the task monitoring interface; the metadata acquisition method further comprises the following steps:

In this step, a small map corresponding to the task execution flow is displayed in the task monitoring interface, and the metadata manager can adjust the portion of the task execution flow displayed in the flow display area by applying a display adjustment operation to the small map.

The method comprises the steps that a content prompt box can be displayed in a small map, content in the content prompt box is content displayed in a flow display area, and at the moment, a metadata manager can trigger the change of a task execution flow displayed in the flow display area by dragging the content prompt box in the small map; alternatively, the change of the task execution flow displayed in the flow display area may be triggered according to the click position by clicking on the minimap.

Here, in order to enable the metadata administrator to determine the completion progress of the metadata collection task, the execution state of each data monitoring node in the metadata collection task may be prompted by displaying a state prompt identifier, so as to intuitively show the completion progress of the metadata collection task.

In one embodiment, the metadata collection method further comprises:

aiming at each data monitoring node, acquiring a metadata acquisition log of the data monitoring node; and determining the metadata acquisition state of the data monitoring node by analyzing the metadata acquisition log, and displaying a state prompt identifier corresponding to the metadata acquisition state around the data monitoring node.

In the step, metadata acquisition logs are recorded in real time in the process of executing metadata acquisition tasks, and when the metadata acquisition states of the data monitoring nodes are determined, the metadata acquisition states of the data monitoring nodes can be determined by analyzing the metadata acquisition logs so as to display corresponding state prompt identifiers;

specifically, aiming at each data monitoring node related to a metadata acquisition task, acquiring a metadata acquisition log of the data monitoring node; analyzing metadata acquisition logs of the data monitoring nodes to determine metadata acquisition states of the data monitoring nodes; and determining a state prompt identifier corresponding to the data monitoring node according to the metadata acquisition state of the data monitoring node, and displaying the state prompt identifier corresponding to the metadata acquisition state around the data monitoring node so as to achieve the purpose of prompting a metadata manager.

The metadata collection status may include ongoing, failed, successful, pending, etc.

Here, the acquired target metadata is required to be distributed to the target data system, but if the target metadata is not changed from the history metadata, it is considered that if metadata distribution is to be performed, the data processing amount of the terminal device is increased, and therefore, before metadata distribution is performed, it is further required to determine whether data distribution is necessary.

Here, in order to facilitate the metadata manager to view the metadata collection log in the task monitoring interface, the task monitoring interface further includes a log display area, where the metadata collection log generated when the metadata collection task is executed is displayed.

In addition, in order to facilitate the metadata manager to view the task attribute information of the metadata acquisition task in the task monitoring interface, the task monitoring interface further comprises a task information display area, and the task attribute information of the metadata acquisition task is displayed in the task information display area, so that the metadata manager can view the task attribute information without exiting the task monitoring interface.

Referring to fig. 4, fig. 4 is a schematic diagram of a task monitoring interface according to an embodiment of the present application. As shown in fig. 4, the task monitoring interface 4a includes a flow display area 4b, a log display area 4c, and a task information display area 4d; the flow display area 4b displays a task execution flow 4b-1 with metadata acquisition tasks and a minimap 4b-2; the task execution flow 4b-1 comprises data monitoring nodes 4b-11 related to metadata acquisition tasks and acquisition sequence flow direction 4b-12 among the data monitoring nodes; the node detail information 4f of the target data monitoring node 4e may be triggered by selecting the target data monitoring node 4e from the data monitoring nodes 4 b-11.

In one embodiment, the metadata collection method further comprises:

determining whether to publish the target metadata to a target data system by comparing the target metadata with historical metadata of the target database; if yes, the target metadata is issued to the target data system, and metadata change information is recorded.

In the step, after the target metadata of the target database are acquired, the target metadata are compared with the historical metadata of the target database, and whether the acquired target metadata are changed compared with the historical metadata of the target database or not is determined.

If yes, determining that the acquired target metadata needs to be subjected to data release so as to synchronize the target metadata into a target data system, and recording metadata change information; otherwise, it may be determined that no data publishing is required, i.e., no publishing of the target metadata acquired this time to the target data system is required.

In one embodiment, a system creation interface is displayed in the graphical user interface; the metadata acquisition method further comprises the following steps:

In the step, if a metadata manager or other users have new requirements of the service system, an interface can be created by means of the system to realize the new addition of the service system; specifically, in response to a system creation operation applied by a metadata administrator or other users in a system creation interface, the creation of the newly added service system is completed by configuring a system class of the service system to be newly added and system attribute information of the service system to be newly added under the system class.

The system attribute information at least comprises service information, authority information, management information and technical information; the service information may include a system name, a system identifier, a system english name, a system chinese name, a system running state, etc.; the management information can comprise a business department, a demand responsible person, an item responsible person, an operation and maintenance responsible person, a creation date, remark information and the like; the technical information may include data source type, date of production, metadata penetration information, and the like.

Referring to fig. 5, fig. 5 is a schematic diagram of a system creation interface according to an embodiment of the present application. As shown in fig. 5, a system creation interface 5b is displayed in the graphical user interface 5a, and a system attribute configuration item 5c is displayed in the system creation interface 5b, so that the metadata administrator can complete configuration of the system category and the system attribute information under the system category by configuring the system attribute configuration item 5c, and create and obtain a new service system.

Here, after the new addition of the service system is completed, a system database which needs to be called when the service is handled for the new addition of the service system is associated.

In one embodiment, a data source configuration interface is displayed in the graphical user interface; the metadata acquisition method further comprises the following steps:

And responding to the data source association operation applied in the data source configuration interface, and determining that the business handling of the newly added business system is a called system database by configuring database attribute information.

In the step, a metadata manager or other users can realize the association of the database and the service system by means of a data source configuration interface; specifically, in response to the data source association operation applied by the metadata administrator or other users in the data source configuration interface, the system database called by the new business system when the business is transacted is determined by configuring the attribute information of the database for the new business system, so that the association between the new business system and the system database is completed.

The database attribute information may include configuration connection information, configuration authority information, and configuration resource group information; the configuration connection information comprises data source classification, a system to which the configuration connection information belongs, a data source name, a data source description, a server, a port and the like; the configuration resource group information may include a resource group name, a resource group service name, a health instance number, and the like.

Referring to fig. 6, fig. 6 is a schematic diagram of a data source association interface according to an embodiment of the present application. As shown in fig. 6, a data source configuration interface 6b is displayed in the graphical user interface 6a, and a database attribute configuration item 6c is displayed in the data source configuration interface 6b, so that a metadata administrator can complete configuration of database attribute information by configuring the database attribute configuration item 6c to associate a newly added service system with a system database.

According to the metadata acquisition method provided by the embodiment of the application, a task creation interface is displayed in a graphical user interface in response to monitoring task creation operation applied in a task management interface; the task creation interface is displayed with a monitoring task configuration item; responding to a monitoring task configuration operation aiming at a monitoring task configuration item, and creating a metadata acquisition task for monitoring a target database by setting a data monitoring node and a data acquisition strategy; and executing a metadata acquisition task according to the data acquisition strategy, and acquiring the corresponding node acquisition data of the target database on each data monitoring node to obtain the target metadata of the target database. Therefore, a metadata manager can customize and acquire the expected target metadata related to the target database by creating metadata acquisition tasks according to requirements, so that acquisition difficulty of the target metadata is simplified, important metadata of the target database can be acquired in a targeted manner, and acquisition efficiency of the metadata is accelerated.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a metadata collection device according to an embodiment of the present application. Providing a graphical user interface through terminal equipment, wherein a task management interface is displayed in the graphical user interface; as shown in fig. 7, the metadata collection apparatus 700 includes:

An interface display module 710 for displaying a task creation interface in the graphical user interface in response to the monitoring task creation operation applied in the task management interface; the task creation interface is used for displaying a monitoring task configuration item;

the task configuration module 720 is configured to create a metadata acquisition task for monitoring the target database by setting a data monitoring node and a data acquisition policy in response to a monitoring task configuration operation for the monitoring task configuration item;

and the data collection module 730 is configured to execute the metadata collection task according to the data collection policy, and obtain the node collection data corresponding to each data monitoring node in the target database, so as to obtain the target metadata of the target database.

Further, a task monitoring list is displayed in the task management interface, wherein the task monitoring list comprises created metadata acquisition tasks; the metadata acquisition device 700 is further configured to:

Further, the metadata collection apparatus 700 is further configured to:

Further, a small map of the task execution flow is displayed in the task monitoring interface; the metadata acquisition device 700 is further configured to:

Further, the metadata collection apparatus 700 is further configured to:

Further, the data acquisition strategy comprises acquisition time and acquisition requirements of each data monitoring node; the data collection module 730 is configured to execute the metadata collection task according to the data collection policy, and when obtaining the target metadata of the target database by acquiring the node collection data corresponding to the target database on each data monitoring node, the data collection module 730 is configured to:

Further, a system creation interface is displayed in the graphical user interface; the metadata acquisition device is also used for:

Further, a data source configuration interface is displayed in the graphical user interface; the metadata acquisition device 700 is further configured to:

The metadata acquisition device provided by the embodiment of the application responds to the monitoring task creation operation applied in the task management interface, and a task creation interface is displayed in a graphical user interface; the task creation interface is displayed with a monitoring task configuration item; responding to a monitoring task configuration operation aiming at a monitoring task configuration item, and creating a metadata acquisition task for monitoring a target database by setting a data monitoring node and a data acquisition strategy; and executing a metadata acquisition task according to the data acquisition strategy, and acquiring the corresponding node acquisition data of the target database on each data monitoring node to obtain the target metadata of the target database. Therefore, a metadata manager can customize and acquire the expected target metadata related to the target database by creating metadata acquisition tasks according to requirements, so that acquisition difficulty of the target metadata is simplified, important metadata of the target database can be acquired in a targeted manner, and acquisition efficiency of the metadata is accelerated.

Referring to fig. 8, fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 8, the electronic device 800 includes a processor 810, a memory 820, and a bus 830.

The memory 820 stores machine-readable instructions executable by the processor 810, when the electronic device 800 is running, the processor 810 communicates with the memory 820 through the bus 830, and when the machine-readable instructions are executed by the processor 810, the steps of the metadata collection method in the method embodiment shown in fig. 1 can be executed, and the specific implementation can be referred to the method embodiment and will not be described herein.

The embodiment of the present application further provides a computer readable storage medium, where a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the steps of the metadata collection method in the embodiment of the method shown in fig. 1 may be executed, and a specific implementation manner may refer to the method embodiment and will not be described herein.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Finally, it should be noted that: the foregoing examples are merely specific embodiments of the present application, and are not intended to limit the scope of the present application, but the present application is not limited thereto, and those skilled in the art will appreciate that while the foregoing examples are described in detail, the present application is not limited thereto. Any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or make equivalent substitutions for some of the technical features within the technical scope of the disclosure of the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. The metadata acquisition method is characterized in that a graphical user interface is provided through terminal equipment, and a task management interface is displayed in the graphical user interface; the metadata acquisition method comprises the following steps:

2. The metadata collection method according to claim 1, wherein a task monitoring list is displayed in the task management interface, and the task monitoring list includes created metadata collection tasks; the metadata acquisition method further comprises the following steps:

3. The metadata collection method according to claim 2, further comprising:

4. The metadata collection method according to claim 2, wherein a small map of the task execution flow is displayed in the task monitoring interface; the metadata acquisition method further comprises the following steps:

5. The metadata collection method according to claim 2, further comprising:

6. The metadata collection method according to claim 1, further comprising:

7. The metadata collection method according to claim 1, wherein the data collection policy includes a collection time and a collection requirement of each data monitoring node; and executing the metadata acquisition task according to the data acquisition strategy, acquiring node acquisition data corresponding to each data monitoring node of the target database, and obtaining target metadata of the target database, wherein the metadata acquisition task comprises the following steps:

8. The metadata collection method according to claim 1, wherein a system creation interface is displayed in the graphical user interface; the metadata acquisition method further comprises the following steps:

9. The metadata collection method according to claim 8, wherein a data source configuration interface is displayed in the graphical user interface; the metadata acquisition method further comprises the following steps:

10. The metadata acquisition device is characterized in that a graphical user interface is provided through terminal equipment, and a task management interface is displayed in the graphical user interface; the metadata acquisition device includes: