Metadata Change Auditing Method, System, Computer Device, and Storage Medium

Abstract

The present invention relates to the field of information and data governance, and discloses a method, system, computer device and storage medium for auditing metadata changes. The method includes: collecting target metadata information of a business system; performing standardization processing on the target metadata information to obtain standard metadata information; constructing a knowledge graph according to the target metadata information, the standard metadata information, and the corresponding relationship between the two; obtaining change-related documents, and inputting the change-related documents and the knowledge graph into a large language model to determine pre-change information; generating a pre-change record according to the pre-change information; obtaining actual change information, and generating an actual change record according to the actual change information; and auditing and comparing the pre-change record and the actual change record. The present invention audits the actual change record through the pre-change record generated by the change-related documents, and can judge whether the changes that have occurred are illegal changes, reducing the communication cost of management personnel.

Description

Technical Field

[0001] The present invention relates to the field of information and data governance, and particularly to a method, a system, a computer device, and a storage medium for auditing metadata changes. Background Art

[0002] At present, the digital economy has become a new driving force for national economic growth and an important breakthrough for economic transformation and the transformation of the human economic form. The quantitative change of super data will trigger the qualitative change of super intelligence, leading to the rapid development of productive forces. The data ability acts on the digital economy to achieve the high-speed development of the digital economy. As the core driving force for the innovative development of the digital economy, data elements not only act on the development of digital industrialization but also include the development of industrial digitalization, that is, the radiation and driving effect of data elements on various sectors of the national economy.

[0003] In the process of digital transformation, the IT department of an enterprise needs to manage a large number of information systems and integrate the data in the information systems into a data platform for unified processing to realize the data value. However, information systems are not static and need to be upgraded, updated, and new business functions need to be expanded along with the business. For the IT department, how to control the changes in information systems, especially the changes in data, has become an important issue. To solve the above problems, the metadata integration module in existing data governance tools is usually adopted. However, if the database structure of the business system changes due to business changes, for the data governance team, it is impossible to confirm whether the change in this metadata is an expected change or an unexpected change, and it is necessary to make a comprehensive judgment by combining information such as the update description of the business system technical team, resulting in high communication costs and low auditing efficiency.

[0004] Therefore, there is an urgent need for a method for auditing metadata changes with high management efficiency and low communication costs. Summary of the Invention

[0005] Therefore, the technical problem to be solved by the present invention is to overcome the problem in the related art that when the metadata in the business system changes, in order to determine whether the change is an expected change or an unexpected change, managers need to make a comprehensive judgment based on information such as the update description, resulting in high communication costs and low auditing efficiency.

[0006] To solve the above technical problem, the present invention provides a method for auditing metadata changes, and the method for auditing metadata changes includes:

[0007] Collecting target metadata information of a business system;

[0008] Performing standardization processing on the target metadata information to obtain standard metadata information;

[0009] Construct a knowledge graph based on the target metadata information, the standard metadata information, and the correspondence between the target metadata information and the standard metadata information;

[0010] Obtain change-related documents, and input the change-related documents and the knowledge graph into a large language model to determine pre-change information; the large language model is configured to determine keyword information based on the change-related documents, and determine the pre-change information based on the keyword information and the knowledge graph;

[0011] Generate a pre-change record according to the pre-change information;

[0012] Obtain actual change information, and generate an actual change record according to the actual change information;

[0013] Audit and compare the pre-change record and the actual change record.

[0014] In an optional implementation manner, the inputting the change-related documents and the knowledge graph into the large language model to determine pre-change information includes:

[0015] Input the change-related documents into the large language model to generate keyword information;

[0016] Input the keyword information and the knowledge graph into the large language model to determine standard change information; the large language model is configured to retrieve and determine the standard change information in the knowledge graph according to the keyword information;

[0017] Input the standard change information and the knowledge graph into the large language model to determine the pre-change information.

[0018] In an optional implementation manner, the obtaining of the actual change information includes:

[0019] When it is detected that the target metadata information changes, generate actual change information and send the actual change information to the message middleware;

[0020] Obtain the actual change information from the message middleware.

[0021] In an optional implementation manner, the generating of the pre-change record according to the pre-change information includes:

[0022] Generate a pre-change record according to the pre-change information, the expected change method corresponding to the pre-change information, and the expected change time;

[0023] The generating of the actual change record according to the actual change information includes:

[0024] Generate an actual change record based on the actual change information, the corresponding actual change method, and the actual change time of the actual change information.

[0025] In an alternative embodiment, the auditing and comparing of the pre-change record and the actual change record includes:

[0026] Determine the matching result of the pre-change record and the actual change record, and determine the matching status of the pre-change record according to the matching result; the matching result includes passed or not passed, and the matching result includes unmatched status or matched status;

[0027] When the matching result of the pre-change record and the actual change record is not passed, determine the matching status of the pre-change record as the unmatched status, and generate an unexpected change warning message; the unexpected change warning message is used to prompt the management personnel that the matching result of the pre-change record and the actual change record is not passed.

[0028] In an alternative embodiment, the method further includes:

[0029] Store the pre-change record and the matching status of the pre-change record in a pre-change database;

[0030] Determine the unmatched change records in the pre-change database according to a preset period; the unmatched change records are the pre-change records in the pre-change database with a matching status of unmatched;

[0031] Determine the metadata information corresponding to the unmatched change records according to the unmatched change records in the pre-change database;

[0032] Audit and compare the unmatched change records in the pre-change database and the metadata information corresponding to the unmatched change records;

[0033] When the matching result of the unmatched change records in the pre-change database and the metadata information corresponding to the unmatched change records is not passed, generate a pre-change delay warning message according to the unmatched change records in the pre-change database; the pre-change delay warning message is used to prompt the management personnel that the metadata information corresponding to the unmatched change records in the pre-change database has not changed.

[0034] In an alternative embodiment, the target metadata information of the business system is stored in a metadata database, and the collecting of the target metadata information of the business system includes:

[0035] Configure the connection information of the metadata database;

[0036] Test whether the connection channel is connected; the connection channel is determined according to the connection information of the metadata database;

[0037] When the connection channel is connected, execute the metadata integration task; the metadata integration task is used to collect the target metadata information of the business system in the metadata database according to the connection information of the metadata database.

[0038] In a second aspect, the present invention provides a metadata change auditing system, and the metadata change auditing system includes:

[0039] A metadata integration module, configured to collect target metadata information of a business system;

[0040] A metadata governance module is connected to the metadata integration module;

[0041] The metadata governance module is configured to perform standardization processing on the target metadata information to obtain standard metadata information; construct a knowledge graph according to the target metadata information, the standard metadata information, and the correspondence between the target metadata information and the standard metadata information;

[0042] A pre-change service module is connected to the metadata governance module;

[0043] The pre-change service module is configured to obtain change-related files, input the change-related files and the knowledge graph into a large language model to determine pre-change information, and generate a pre-change record according to the pre-change information; the large language model is configured to determine keyword information according to the change-related files, and determine pre-change information according to the keyword information and the knowledge graph;

[0044] A metadata change auditing module is connected to the pre-change service module;

[0045] The metadata change auditing module is configured to obtain actual change information, generate an actual change record according to the actual change information; perform auditing and comparison on the pre-change record and the actual change record.

[0046] In a third aspect, the present invention provides a computer device, including: a memory and a processor, which are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to execute the metadata change auditing method according to the first aspect or any corresponding embodiment thereof.

[0047] In a fourth aspect, the present invention provides a computer-readable storage medium, on which a computer instruction is stored, and the computer instruction is used to cause a computer to execute the metadata change auditing method according to the first aspect or any corresponding embodiment thereof.

[0048] In a fifth aspect, the present invention provides a computer program product, including computer instructions for causing a computer to execute the metadata change auditing method according to the first aspect or any corresponding embodiment thereof as described above.

[0049] The technical solution provided by the present invention has the following technical effects:

[0050] Through the text parsing and processing capabilities of the large language model and the knowledge graph constructed based on metadata information, the present invention can determine pre-change records from the change-related documents. By auditing and comparing the pre-change records with the actual change records, it is judged whether the change corresponding to the actual change record is an expected change or an unexpected change. Through the above technical solution for auditing and comparison, it is not necessary for the management personnel to have an in-depth understanding of the change technology and change details of the business system, which can assist the management personnel in managing metadata information, reduce communication costs, reduce workload, and improve auditing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required to be used in the description of the specific embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0052] Figure 1 is a flowchart of the metadata change auditing method according to an embodiment of the present invention;

[0053] Figure 2 is an overall flowchart of the metadata change auditing method according to an embodiment of the present invention;

[0054] Figure 3 is a structural diagram of the metadata change auditing system according to an embodiment of the present invention;

[0055] Figure 4 is a hardware structural diagram of the computer device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0056] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

[0057] Therefore, the embodiments of the present invention provide a method, a system, a computer device and a storage medium for auditing metadata changes, so as to solve the problem in the related art that when the metadata in the business system changes, in order to determine whether the change is an expected change or an unexpected change, managers need to make a comprehensive judgment based on information such as update descriptions, resulting in high communication costs and low auditing efficiency.

[0058] According to the embodiments of the present invention, an embodiment of a method for auditing metadata changes is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0059] Figure 1 It is a flowchart of a method for auditing metadata changes according to the embodiments of the present invention.

[0060] As Figure 1 shown, a method for auditing metadata changes provided in the embodiments of the present invention can be applied to a metadata change auditing system, which can be a metadata change auditing system and can include: a metadata management module, a pre-change service module, and a metadata change auditing module. The metadata management module includes: a metadata integration module and a metadata governance module.

[0061] The method for auditing metadata changes includes:

[0062] S101: Collect the target metadata information of the business system.

[0063] In this embodiment, the target metadata information of the business system is stored in the metadata database. The specific steps of S101 for collecting the target metadata information of the business system include:

[0064] S1011: Configure the connection information of the metadata database.

[0065] In this embodiment, the connection information of the metadata database can be used as data source connection information, which can include the access address, port, username, password, etc. of the metadata database.

[0066] S1012: Test whether the connection channel is connected.

[0067] In this embodiment, the connection channel is determined according to the connection information of the metadata database. The connection channel is the communication channel between the metadata integration module and the metadata database.

[0068] S1013: When the connection channel is connected, execute the metadata integration task. The metadata integration task is used to collect the target metadata information of the business system in the metadata database according to the connection information of the metadata database.

[0069] In this embodiment, the target metadata information of the business system may include the connection information of the metadata database, table list, field list, system name, etc. The table list may include: table name, Chinese table name, and table annotation information. The field list may include: field name, table name to which it belongs, Chinese field name, field type, and field annotation information.

[0070] The metadata change auditing method provided by the embodiments of the present invention can be applied to various types of business systems. As an example, if the business system is a human resource management system, then the above S101 to collect the target metadata information of the business system is specifically as follows: The user configures the connection information of the metadata database of the human resource management system through the metadata integration module, fills in the access address, port, username, password, etc. of the metadata database, and the metadata change auditing system tests whether the connection channel to the metadata database is connected and saves the connection information of the data database to the database of the metadata change auditing system. The metadata integration module schedules the metadata integration task regularly, accesses the corresponding metadata database according to the connection information of the metadata database of the metadata change auditing system, reads the target metadata information, and saves it to the database of the metadata change auditing system.

[0071] S102: Perform standardization processing on the target metadata information to obtain standard metadata information, and construct a knowledge graph based on the target metadata information, standard metadata information, and the corresponding relationship between the target metadata information and the standard metadata information.

[0072] In this embodiment, the metadata governance module can execute the steps of S102 above. Performing standardization processing on the target metadata information to obtain standard metadata information specifically includes: performing word segmentation and synonym processing on the target metadata information to obtain words to be standardized, obtaining a pre-constructed data standard term table, and searching for the standard terms corresponding to the words to be standardized in the data standard term table, so as to obtain standard metadata information. As an example, after performing word segmentation processing and standardization conversion on the table name, field name, field annotation information, etc., standard metadata information, as well as the corresponding relationship between the target metadata information and the standard metadata information, are obtained. The knowledge graph constructed based on the target metadata information, standard metadata information, and the corresponding relationship between the target metadata information and the standard metadata information can be stored in the knowledge graph engine for semantic association, facilitating the large language model to parse specific tables or fields from the semantics.

[0073] As an example, data governance personnel use the data governance module of the metadata change audit system to standardize the target metadata information of the collected business system. After the data governance module performs word segmentation and synonym comparison on the table, field and corresponding annotation information, it matches the closest standard term in the data standard term table and forms an association relationship between the target metadata information and the corresponding standard term. For example: a target metadata information is collected from the human resources internal management system, and the "employee basic information table" contains a field named "employee name", and there is a standard term called "employee name" in the standard term table. At this time, "employee name" can be segmented into two words, "employee" and "name", "employee" is consistent with the standard term, and "name" and "name" are synonyms, so "employee name" is "employee name" after standardization. The above target metadata information includes "employee name", the words to be standardized include "employee", "name" and "name", the standard term includes "employee name", and the standard metadata information includes "employee name". The metadata change audit system saves the original field name and the standardized field name, and establishes an association between "employee name" and "employee name". After completing the standardization process, the data governance module can save the target metadata information, the standard metadata information after standardization, and the correspondence between the target metadata information and the standard metadata information to the knowledge graph engine. For example: the knowledge graph engine contains 2 entities, the field information entity: "employee name", the standard term entity: "employee name", and the connection between the two entities "standardization".

[0074] S103: Obtain change-related documents, input the change-related documents and the knowledge graph into the large language model to determine pre-change information, and generate a pre-change record based on the pre-change information.

[0075] In the art, a large language model is configured to determine keyword information based on change-related files, and determine pre-change information based on the keyword information and a knowledge graph.

[0076] In this field, the pre-change service module can perform the above step S103. Before the business system is changed, the technical staff needs to provide change-related documents. The change-related documents can be system upgrade plans or update instructions or DMLSQL document information.

[0077] In this embodiment, the large language model includes but is not limited to llama3, GPT-3, BERT, Transformer-X and other models. In this embodiment, based on the actual application scenario of the present invention, the large language model can be trained in a targeted manner to improve the accuracy of determining the pre-change information.

[0078] In the scenario targeted by the present invention, in addition to tasks related to data governance, the management personnel also need to control changes to the business system. Specifically, due to changes in the business system, business upgrades, etc., the database structure changes, and the change in the database leads to a change in metadata. The technical means usually adopted by the management personnel for the above changes are as follows: After manually checking according to the change-related documents provided by the technical personnel, compare with the change in metadata to confirm whether the change in the database structure meets the expectations.

[0079] In this process, the technical personnel of the business system provide a system upgrade plan, update description, or DML SQL document information to the management personnel before the system upgrade. The management personnel upload the change-related documents through the functions provided by the metadata change audit system. After the pre-change service module receives the change-related documents and saves them, it uploads the documents to the large language model and parses the pre-change information by asking questions. After the large language model semantically parses the change-related documents, it analyzes the metadata information that needs to be changed, compares it with the metadata information in the knowledge graph engine, parses the specific table and field information to be changed, generates a pre-change record, and stores it in the pre-change database.

[0080] S104: Obtain the actual change information, generate an actual change record according to the actual change information, and conduct an audit comparison between the pre-change record and the actual change record.

[0081] In this embodiment, the metadata change audit module can execute the steps of S104 above. The above-mentioned obtaining of the actual change information specifically includes: When it is detected that the target metadata information has changed, generate the actual change information and send the actual change information to the message middleware. Obtain the actual change information from the message middleware. In this embodiment, the metadata governance module can generate a metadata change event when it detects a difference in the target metadata information before and after, determine that the target metadata information has changed, generate the actual change information according to the difference in the target metadata information before and after, and send the actual change information to the message middleware. The metadata change audit module can obtain the actual change information from the message middleware.

[0082] In this embodiment, the steps of S104 above are executed for each pre-change record and the actual change information corresponding to the pre-change record.

[0083] In an alternative embodiment, S103 inputs the change-related document and the knowledge graph into the large language model to determine the pre-change information, including:

[0084] S1031: Input the change-related document into the large language model to generate keyword information.

[0085] S1032: Input the keyword information and the knowledge graph into the large language model to determine the standard change information.

[0086] In this embodiment, the large language model is configured to retrieve and determine the standard change information in the knowledge graph according to the keyword information.

[0087] In this embodiment, the standard change information is the first parsing result of the large language model. First, the superior entity can be retrieved and determined in the knowledge graph according to the keyword information. The superior entity can be the database table name, database annotation, standardized table name, and the same applies to fields. Then, the subordinate entity, such as a table or a field, can be inferred through the corresponding relationship. In this embodiment, the table and field to be changed cannot be directly determined through the knowledge graph and the keyword information, and only the first parsing result can be obtained. To obtain more accurate tables and fields to be changed, the standard change information and the knowledge graph need to be input into the large language model for further parsing.

[0088] S1033: Input the standard change information and the knowledge graph into the large language model to determine the pre-change information.

[0089] In this embodiment, the pre-change information is the second parsing result of the large language model and is the metadata information that should actually change in the business system. The pre-change information can be used as a metadata change request form for the business system. In this embodiment, a part of the change information in the standard change information can be used as the pre-change information through the parsing of the large language model. Through multiple parsings of the large language model, the accuracy of determining the pre-change information can be improved by performing the second parsing on the basis of the first parsing.

[0090] As an example, if the large language model is llama3, S1031 will input the relevant files to the large language model to generate keyword information, specifically including: based on the semantic analysis and code analysis capabilities of the llama3 large language model, using a specific prompt to ask questions to the llama3 large language model, and having the llama3 large language model parse the content of the metadata database changes from the relevant files (the relevant files include unstructured documents such as system upgrade plans, update descriptions, and DML SQL). This will be used as keyword information, such as the systems, tables, fields, and change times involved. For example: in system upgrade plans and update descriptions, the change descriptions are generally in text form. For example: adding a "staff seniority" field to the "employee basic information table", then three keyword information can be inferred: (1) affected system: human resource management system, (2) affected table: employee basic information table, (3) affected content: adding a "staff seniority" field. If the uploaded information is a DML SQL file, the above three keyword information can also be inferred through SQL statement parsing, and the table names and field names are relatively accurate. At the same time, the expected change method and expected change time can also be parsed from the upgrade plan and update description. The expected change method can include methods such as adding, replacing, and deleting.

[0091] After obtaining the keyword information, the standard change information can be determined through a technical means that combines the llama3 large language model with the Graph RAG technology. The llama3 large language model retrieves the metadata information of relevant tables and fields in the knowledge graph based on the keyword information as the standard metadata information. And the standard metadata information and the knowledge graph are used as context to input into the large language model. Based on the GraphRAG technology, the large language model matches the knowledge graph, and through the matching of key data such as systems and tables, finally parses the metadata information of the actual data tables that need to be changed, and uses the metadata information of the actual data tables that need to be changed as the pre-change information.

[0092] After determining the pre-change information by inputting the standard change information and the knowledge graph into the large language model, the background service generates a pre-change record based on the pre-change information, the expected change method corresponding to the pre-change information, and the expected change time. This pre-change record includes metadata identifiers, table name change information, field change information, matching status, expected change time, etc., and saves the pre-change record in the pre-change database of the system.

[0093] In an optional implementation manner, generating a pre-change record according to the pre-change information in S103 includes: generating a pre-change record according to the pre-change information, the expected change method corresponding to the pre-change information, and the expected change time.

[0094] In this embodiment, the pre-change service module can generate a pre-change record according to the pre-change information, the expected change method corresponding to the pre-change information, and the expected change time.

[0095] In an alternative embodiment, generating the actual change record according to the actual change information in S104 includes: generating the actual change record according to the actual change information, the actual change method corresponding to the actual change information, and the actual change time.

[0096] In this embodiment, the metadata change auditing module can generate the actual change record according to the actual change information, the actual change method corresponding to the actual change information, and the actual change time.

[0097] In an alternative embodiment, the auditing and comparison of the pre-change record and the actual change record in S104 includes:

[0098] Sa1: Determine the matching result of the pre-change record and the actual change record, and determine the matching status of the pre-change record according to the matching result.

[0099] In this embodiment, the matching result includes passed or not passed, and the matching result includes unmatched status or matched status.

[0100] Sa2: When the matching result of the pre-change record and the actual change record is not passed, determine the matching status of the pre-change record as unmatched status, and generate an unexpected change warning message.

[0101] In this embodiment, the unexpected change warning message is used to prompt the management personnel that the matching result of the pre-change record and the actual change record is not passed. As an example, the unexpected change warning message can be stored in the database, and when the background service queries the unexpected change warning message, the unexpected change warning message is prompted to the management personnel.

[0102] In this embodiment, when the matching result of the pre-change record and the actual change record is passed, determine the matching status of the pre-change record as matched status, and audit and compare the next pre-change record and its corresponding actual change record.

[0103] In this embodiment, the actual change records can be compared one by one with the pre-change records stored in the pre-change database through the metadata change auditing module. The content of the audit is whether the change content such as the system name, table name, and field name that actually triggers the change is consistent with the change content such as the system name, table name, and field name in the registered change information (the pre-change records stored in the pre-change database). If so, it is determined that the matching result of the pre-change record and the actual change record passes, and the matching status of the pre-change record stored in the pre-change database is updated to the matched status, and the next change information is audited. If not, it is determined that the matching result of the pre-change record and the actual change record fails, and the matching status of the pre-change record stored in the pre-change database is updated to the unmatched status, and an unexpected change warning message is generated. The unexpected change warning message is stored in the database. After the background service queries the unexpected change warning message, it is prompted to the management personnel.

[0104] In this embodiment, the above auditing process may involve some detailed processing. For example, when a new table is added, since the addition of both the table and the fields belongs to metadata changes, but generally in materials such as the provided upgrade plan, only the new table will be clarified and the specific field list will not be clarified. Therefore, in the specific auditing process, there will be a situation of mutual filtering between changes. The above problems can be solved by conventional technical means in this field and will not be specifically described in the present invention. The above embodiment mainly illustrates the method of change auditing.

[0105] In the present invention, in addition to the above change auditing method, the metadata change auditing method further includes another auditing method:

[0106] Sb1: Store the pre-change record and the matching status of the pre-change record in the pre-change database.

[0107] Sb2: Determine the unmatched change records in the pre-change database according to a preset period.

[0108] In this embodiment, the unmatched change records are the pre-change records in the pre-change database with the matching status of unmatched.

[0109] Sb3: Determine the latest metadata information corresponding to the unmatched change records according to the unmatched change records in the pre-change database.

[0110] In this embodiment, the metadata information corresponding to the unmatched change records is the metadata information corresponding to the unmatched change records.

[0111] Sb4: Audit and compare the unmatched change records in the pre-change database with the metadata information corresponding to the unmatched change records.

[0112] Sb5: When the matching result of the unmatched change records and the metadata information corresponding to the unmatched change records in the pre-change database fails, generate a pre-change delay warning message based on the unmatched change records in the pre-change database.

[0113] In this embodiment, the pre-change delay warning message is used to prompt the management personnel that the metadata information corresponding to the unmatched change records in the pre-change database has not changed, and prompt the management personnel to perform further processing.

[0114] The metadata change auditing module can scan the pre-change information in the pre-change database according to a preset period, determine the unmatched change records in the pre-change database. The unmatched change records are specifically the pre-change records whose matching status in the pre-change database remains unmatched within a preset duration, which means that the pre-change information has been in an unmatched state for a long time. At this time, it is necessary to determine the latest metadata information corresponding to the unmatched change records based on the unmatched change records in the pre-change database, and conduct an auditing comparison between the unmatched change records and the latest metadata information corresponding to the unmatched change records. When the matching result of the unmatched change records and the metadata information corresponding to the unmatched change records in the pre-change database passes, update the matching status of the unmatched change records to the matched state.

[0115] The overall process of the metadata change auditing method proposed in the embodiment of the present invention is as Figure 2 shown. Conducting metadata change auditing based on the technical solution of the present invention can find out unexpected changes through auditing, without the need for management personnel to have an in-depth understanding of the change details of the business system, reducing the workload of management personnel's intervention in metadata changes. There is no need for management personnel to have an in-depth understanding of the business system like technical personnel, reducing the communication between management personnel and technical personnel. During the communication process between management personnel and technical personnel, management personnel can improve the communication efficiency with technical personnel based on information such as pre-change information, actual change information, and matching results. The technical solution of the present invention can compare and audit the system upgrade plan, update description with the actual changes in the database through the semantic understanding ability of the large language model and the knowledge graph, assisting management personnel in controlling database changes.

[0116] It should be noted that the content not detailedly described in the specification of the present invention belongs to the well-known technology of those skilled in the art.

[0117] In this embodiment, a metadata change auditing system is also provided. A single system is used to implement the above-mentioned embodiments and optional implementation manners, and those that have been described will not be repeated. As used hereinafter, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the systems described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0118] Figure 3 It is a schematic structural diagram of a metadata change auditing system according to an embodiment of the present invention.

[0119] The present invention provides a metadata change auditing system, as Figure 3 shown, the metadata change auditing system includes:

[0120] A metadata integration module 11, configured to collect target metadata information of a business system.

[0121] A metadata governance module 12 is connected to the metadata integration module 11.

[0122] The metadata governance module 12 is configured to perform standardization processing on the target metadata information to obtain standard metadata information, and construct a knowledge graph based on the target metadata information, the standard metadata information, and the correspondence relationship between the target metadata information and the standard metadata information.

[0123] A pre-change service module 13 is connected to the metadata governance module 12.

[0124] The pre-change service module 13 is configured to obtain change-related documents, input the change-related documents and the knowledge graph into a large language model to determine pre-change information, and generate a pre-change record according to the pre-change information. The large language model is configured to determine keyword information according to the change-related documents, and determine pre-change information according to the keyword information and the knowledge graph.

[0125] A metadata change auditing module 14 is connected to the pre-change service module 13.

[0126] The metadata change auditing module 14 is configured to obtain actual change information, and generate an actual change record according to the actual change information. The pre-change record and the actual change record are audited and compared.

[0127] In an optional implementation manner, the target metadata information of the business system is stored in a metadata database, and the metadata integration module 11 includes:

[0128] A first processing unit, configured to configure connection information of the metadata database.

[0129] A second processing unit, configured to test whether a connection channel is connected. The connection channel is determined according to the connection information of the metadata database.

[0130] A third processing unit, configured to perform a metadata integration task when the connection channel is connected. The metadata integration task is used to collect the target metadata information of the business system in the metadata database according to the connection information of the metadata database.

[0131] In an alternative embodiment, the pre-change service module 13 includes:

[0132] A first processing unit for inputting change-related files into a large language model to generate keyword information.

[0133] A second processing unit for inputting the keyword information and the knowledge graph into the large language model to determine standard change information. The large language model is configured to retrieve and determine the standard change information in the knowledge graph according to the keyword information.

[0134] A third processing unit for inputting the standard change information and the knowledge graph into the large language model to determine pre-change information.

[0135] In an alternative embodiment, the pre-change service module 13 further includes a fourth processing unit.

[0136] The fourth processing unit is used to generate a pre-change record according to the pre-change information, the expected change method corresponding to the pre-change information, and the expected change time.

[0137] In an alternative embodiment, the metadata governance module 12 is further configured to generate actual change information when detecting that the target metadata information has changed, and send the actual change information to the message middleware.

[0138] The metadata change auditing module 14 includes a first processing unit.

[0139] The first processing unit is used to obtain the actual change information from the message middleware.

[0140] In an alternative embodiment, the metadata change auditing module 14 further includes a second processing unit.

[0141] The second processing unit is used to generate an actual change record according to the actual change information, the actual change method corresponding to the actual change information, and the actual change time.

[0142] In an alternative embodiment, the metadata change auditing module 14 further includes a third processing unit.

[0143] The third processing unit includes:

[0144] A first processing subunit for determining the matching result of the pre-change record and the actual change record, and determining the matching status of the pre-change record according to the matching result. The matching result includes pass or fail, and the matching result includes unmatched status or matched status.

[0145] A second processing subunit, configured to determine that the matching status of the pre-change record is an unmatched status when the matching result of the pre-change record and the actual change record fails, and generate an unexpected change warning message. The unexpected change warning message is used to prompt the management personnel that the matching result of the pre-change record and the actual change record fails.

[0146] In an alternative embodiment, the metadata change auditing module 14 further includes a fourth processing unit.

[0147] The fourth processing unit includes:

[0148] A first processing subunit, configured to store the pre-change record and the matching status of the pre-change record into the pre-change database.

[0149] A second processing subunit, configured to determine the unmatched change records in the pre-change database according to a preset period. The unmatched change records are the pre-change records in the pre-change database with a matching status of unmatched.

[0150] A third processing subunit, configured to determine the metadata information corresponding to the unmatched change records according to the unmatched change records in the pre-change database.

[0151] A fourth processing subunit, configured to audit and compare the unmatched change records in the pre-change database and the metadata information corresponding to the unmatched change records.

[0152] A fifth processing subunit, configured to generate a pre-change delay warning message according to the unmatched change records in the pre-change database when the matching result of the unmatched change records in the pre-change database and the metadata information corresponding to the unmatched change records fails. The pre-change delay warning message is used to prompt the management personnel that the metadata information corresponding to the unmatched change records in the pre-change database has not changed.

[0153] The further function descriptions of the above-mentioned modules and units are the same as those in the corresponding embodiments above, and will not be elaborated here.

[0154] The metadata change auditing system in this embodiment is presented in the form of functional units. Here, the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and a memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0155] The embodiment of the present invention further provides a computer device having the above Figure 3 shown metadata change auditing system.

[0156] Please refer to Figure 4 , Figure 4is a schematic diagram of the hardware structure of the computer device according to an embodiment of the present invention, as Figure 4 shown. The computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including a high-speed interface and a low-speed interface. Each component communicates with each other using different buses and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed within the computer device, including instructions stored in the memory or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In an alternative embodiment, if needed, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (such as an array of servers, a set of blade servers, or a multi-processor device). Figure 4 In

[0157] FIG. 4, one processor 10 is taken as an example.

[0158] The processor 10 can be a central processing unit, a network processor, or a combination thereof. Among them, the processor 10 can further include a hardware chip. The above hardware chip can be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The above programmable logic device can be a complex programmable logic device, a field programmable gate array, a general array logic, or any combination thereof.

[0159] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0160] The memory 20 can include a storage program area and a storage data area. Among them, the storage program area can store an operating system and application programs required for at least one function. The storage data area can store data created according to the use of the computer device. In addition, the memory 20 can include a high-speed random access memory and can also include a non-transitory memory, such as at least one disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In an alternative embodiment, the memory 20 can optionally include a memory remotely set relative to the processor 10, and these remote memories can be connected to the computer device through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and a combination thereof.

[0161] The computer device further includes a communication interface 30 for the computer device to communicate with other devices or communication networks.

[0162] An embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or be implemented as computer code that can be recorded on a storage medium, or be implemented by downloading through a network and originally stored in a remote storage medium or a non-transitory machine-readable storage medium and will be stored in a local storage medium, so that the method described herein can be stored as such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid-state drive, etc. Further, the storage medium can also include a combination of the above-mentioned types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by the computer, the processor, or the hardware, the method shown in the above embodiment is implemented.

[0163] A part of the present invention can be applied as a computer program product, such as computer program instructions. When executed by a computer, through the operation of the computer, the method and / or technical solution according to the present invention can be invoked or provided. Those skilled in the art should be able to understand that the forms of existence of computer program instructions in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways for computer program instructions to be executed by a computer include, but are not limited to: the computer directly executes the instructions, or the computer compiles the instructions and then executes the corresponding compiled program, or the computer reads and executes the instructions, or the computer reads and installs the instructions and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0164] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A metadata change auditing method, characterized in that, It includes: Collecting the target metadata information of the business system; Performing standardization processing on the target metadata information to obtain standard metadata information; Constructing a knowledge graph based on the target metadata information, the standard metadata information, and the correspondence between the target metadata information and the standard metadata information; Obtaining change-related documents, and inputting the change-related documents and the knowledge graph into a large language model to determine pre-change information; The large language model is configured to determine keyword information based on the change-related documents, and determine pre-change information based on the keyword information and the knowledge graph; The change-related documents include: system upgrade plans, update instructions, or DML SQL document information provided to managers before system upgrade; the pre-change information is the metadata information that should actually change in the business system, which is the metadata change application form of the business system; Generating a pre-change record based on the pre-change information; Obtaining actual change information, and generating an actual change record based on the actual change information; Comparing and auditing the pre-change record and the actual change record to determine whether the change corresponding to the actual change record is an expected change or an unexpected change; Inputting the change-related documents and the knowledge graph into the large language model to determine pre-change information, including: Inputting the change-related documents into the large language model to generate keyword information; the keyword information includes the content of the change in the metadata database parsed from the change-related documents; Inputting the keyword information and the knowledge graph into the large language model to determine standard change information; the large language model is configured to retrieve and determine standard change information in the knowledge graph based on the keyword information; Inputting the standard change information and the knowledge graph into the large language model to determine pre-change information.

2. The method according to claim 1, characterized in that, The obtaining of the actual change information includes: When it is detected that the target metadata information has changed, generating actual change information and sending the actual change information to the message middleware; Obtaining the actual change information from the message middleware.

3. The method according to claim 1, characterized in that, The generating of the pre-change record according to the pre-change information includes: Generating a pre-change record according to the pre-change information, the expected change method corresponding to the pre-change information, and the expected change time; The generating of the actual change record according to the actual change information includes: Generating an actual change record according to the actual change information, the actual change method corresponding to the actual change information, and the actual change time.

4. The method according to claim 1, wherein The comparing and auditing of the pre-change record and the actual change record includes: Determining the matching result of the pre-change record and the actual change record, and determining the matching status of the pre-change record according to the matching result; the matching result includes passed or not passed, and the matching result includes unmatched status or matched status; When the matching result of the pre-change record and the actual change record is not passed, determining the matching status of the pre-change record as unmatched status, and generating an unexpected change warning information; the unexpected change warning information is used to prompt the manager that the matching result of the pre-change record and the actual change record is not passed.

5. The method according to claim 4, wherein The method further includes: Storing the pre-change record and the matching status of the pre-change record into a pre-change database; Determine the unmatched change records in the pre-change database according to a preset period; the unmatched change records are pre-change records with an unmatched status in the pre-change database; Determine the metadata information corresponding to the unmatched change records according to the unmatched change records in the pre-change database; Perform an audit comparison on the unmatched change records in the pre-change database and the metadata information corresponding to the unmatched change records; When the matching result of the unmatched change records in the pre-change database and the metadata information corresponding to the unmatched change records fails, generate a pre-change delay warning message according to the unmatched change records in the pre-change database; the pre-change delay warning message is used to prompt the management personnel that the metadata information corresponding to the unmatched change records in the pre-change database has not changed.

6. The method according to claim 1, wherein The target metadata information of the business system is stored in the metadata database, and collecting the target metadata information of the collection business system includes: Configure the connection information of the metadata database; Test whether the connection channel is connected; the connection channel is determined according to the connection information of the metadata database; When the connection channel is connected, execute a metadata integration task; the metadata integration task is used to collect the target metadata information of the business system in the metadata database according to the connection information of the metadata database.

7. A metadata change auditing system, characterized in that, Including: A metadata integration module for collecting the target metadata information of the business system; The metadata governance module is connected to the metadata integration module; A metadata governance module for performing standardization processing on the target metadata information to obtain standard metadata information; Construct a knowledge graph according to the target metadata information, the standard metadata information, and the corresponding relationship between the target metadata information and the standard metadata information; The pre-change service module is connected to the metadata governance module; The pre-change service module is used to obtain change-related files, input the change-related files and the knowledge graph into a large language model to determine pre-change information, and generate pre-change records according to the pre-change information; The large language model is configured to determine keyword information according to the change-related files, and determine pre-change information according to the keyword information and the knowledge graph; The change-related files include: the system upgrade plan, update instructions, or DML SQL document information provided to the management personnel before the system upgrade; the pre-change information is the metadata information that should actually change in the business system, and is a metadata change request form for the business system; The metadata change audit module is connected to the pre-change service module; The metadata change audit module is used to obtain the actual change information and generate actual change records according to the actual change information; perform an audit comparison on the pre-change records and the actual change records to determine whether the change corresponding to the actual change record is an expected change or an unexpected change; The pre-change service module includes: A first processing unit for inputting the change-related files into the large language model to generate keyword information; the keyword information includes the content of the change in the metadata database parsed from the change-related files; A second processing unit for inputting keyword information and a knowledge graph into a large language model to determine standard change information; the large language model is configured to retrieve and determine standard change information in the knowledge graph according to the keyword information; A third processing unit for inputting the standard change information and the knowledge graph into the large language model to determine pre-change information.

8. A computer device, characterized in that, Comprising: A memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to execute the metadata change auditing method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, Computer instructions are stored on the computer-readable storage medium, and the computer instructions are used to cause a computer to execute the metadata change auditing method according to any one of claims 1 to 6.

Images