Heterogeneous metadata verification method and device, equipment and medium
By obtaining the database type and project information of the target metadata, and then obtaining the corresponding verification rule information, the problem of traditional tools being unable to perform accurate verification under multiple database types is solved, and efficient verification of heterogeneous metadata is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-03
- Publication Date
- 2026-04-10
AI Technical Summary
Traditional verification tools struggle to accurately verify heterogeneous metadata across various database types.
By obtaining the database type and/or project information of the target metadata, the corresponding target verification rule information is obtained, and the metadata is verified based on these rules.
It enables accurate verification of heterogeneous metadata, improves the accuracy and adaptability of verification, and supports compatible verification for multiple database types.
Smart Images
Figure CN121833674A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of heterogeneous metadata verification, and in particular to a heterogeneous metadata verification method, device, equipment and medium. BACKGROUND
[0002] In the process of metadata verification, the traditional verification tool usually presets the syntax and constraint rules of a certain type of database (such as Oracle or MySQL), and can only verify the metadata of a certain database in the same platform, and it is difficult to accurately verify the metadata in the scene of multiple database types. How to accurately verify the heterogeneous metadata is a technical problem that needs to be solved. SUMMARY
[0003] The present application provides a heterogeneous metadata verification method, device, equipment and medium, which can obtain the verification rules corresponding to the metadata, and verify the metadata based on the verification rules corresponding to the metadata.
[0004] According to an aspect of the present application, a heterogeneous metadata verification method is provided, which comprises:
[0005] Obtain target metadata, and determine the database type and / or project information of the target metadata; the target metadata is one of the heterogeneous metadata;
[0006] Obtain target verification rule information corresponding to the target metadata based on the database type and / or project information;
[0007] Verify the target metadata based on the target verification rule information to obtain a verification result.
[0008] According to another aspect of the present application, a heterogeneous metadata verification device is provided, which comprises:
[0009] A target metadata obtaining module is configured to obtain target metadata, and determine the database type and / or project information of the target metadata; the target metadata is one of the heterogeneous metadata;
[0010] A target verification rule information determining module is configured to obtain target verification rule information corresponding to the target metadata based on the database type and / or project information;
[0011] A verification module is configured to verify the target metadata based on the target verification rule information to obtain a verification result.
[0012] According to another aspect of the present application, an electronic device is provided, which comprises:
[0013] At least one processor; and
[0014] a memory connected with the at least one processor in communication; wherein,
[0015] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the checking method of the heterogeneous metadata according to any one of the embodiments of the present application.
[0016] According to another aspect of the present application, a computer readable storage medium is provided, which stores computer instructions for enabling a processor to implement the checking method of the heterogeneous metadata according to any one of the embodiments of the present application when executed by the processor.
[0017] The technical solution of the embodiments of the present application comprises: obtaining target metadata, and determining the database type and / or project information of the target metadata; the target metadata is one of the heterogeneous metadata; obtaining target checking rule information corresponding to the target metadata based on the database type and / or project information; and checking the target metadata based on the target checking rule information to obtain a checking result. The present solution can accurately check the metadata based on the checking rule of the database corresponding to the target metadata and / or the checking rule of the project information, thereby avoiding the solution of checking the heterogeneous metadata by using a set of checking rules, and improving the checking accuracy.
[0018] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the present application, nor is it used to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS
[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative effort.
[0020] Figure 1 is a flowchart of a checking method of heterogeneous metadata according to the first embodiment of the present application;
[0021] Figure 2 is a flowchart of a checking method of heterogeneous metadata according to the second embodiment of the present application;
[0022] Figure 3 is a metadata checking rule loading flowchart according to the second embodiment of the present application;
[0023] Figure 4 is a structural schematic diagram of a heterogeneous metadata verification device according to Embodiment Three of the present application;
[0024] Figure 5 is a structural schematic diagram of an electronic device for implementing a heterogeneous metadata verification method according to the present application. DETAILED DESCRIPTION
[0025] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts should fall within the scope of the present application.
[0026] It should be noted that the terms "first", "second", "target" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to the process, method, product or device.
[0027] Embodiment One
[0028] Figure 1 A flowchart of a heterogeneous metadata verification method according to Embodiment One of the present application is provided, which can be applicable to the case of verifying heterogeneous metadata. The method can be executed by a heterogeneous metadata verification device, which can be realized in the form of hardware and / or software, and can be configured in an electronic device with data processing capability. As shown in the figure, the method comprises: Figure 1
[0029] S110, obtaining target metadata and determining the database type and / or item information of the target metadata; the target metadata is one of the heterogeneous metadata.
[0030] The target metadata can be metadata of a database table, which can be obtained during a database table design process. The target metadata can correspond to any database type, and different target metadata can correspond to different database types, i.e., the target metadata can be one of heterogeneous metadata. Any target metadata in the heterogeneous metadata can be processed in the same manner, and therefore, only the verification process for the target metadata is described.
[0031] Specifically, since the metadata to be verified in the embodiments of the present application can be metadata of any database type, after obtaining the target metadata, the database type corresponding to the target metadata needs to be determined for targeted verification.
[0032] Further, since different projects can have different data specifications, even for the same database type, different projects can have different data specifications, and therefore, the project information corresponding to the target metadata also needs to be obtained to determine the verification content based on the project information and perform verification.
[0033] In an optional embodiment, the database type of the target metadata can be determined, and accordingly, in a subsequent step, the target verification rule information corresponding to the target metadata is obtained based on the database type, and the metadata is verified based on the target verification rule information.
[0034] In another optional embodiment, the project information of the target metadata can be determined, and accordingly, in a subsequent step, the target verification rule information corresponding to the target metadata is obtained based on the project information, and the metadata is verified based on the target verification rule information.
[0035] In an optional embodiment, the database type and the project information of the target metadata can be determined, and accordingly, in a subsequent step, the target verification rule information corresponding to the target metadata is obtained based on the database type and the project information, and the metadata is verified based on the target verification rule information.
[0036] S120, obtaining target verification rule information corresponding to the target metadata based on the database type and / or the project information.
[0037] Specifically, after the database type and / or the project information are determined, the target verification rule information corresponding to the target metadata can be obtained from the pre-set verification rule information based on the database type and / or the project information, for subsequent accurate verification.
[0038] S130, verifying the target metadata based on the target verification rule information to obtain a verification result.
[0039] Specifically, after the target check rule information is obtained, a rule engine for metadata check is loaded to check the target metadata based on the target check rule information, and a check result is obtained.
[0040] The technical scheme of the embodiment of the application comprises: obtaining target metadata, and determining a database type and / or project information of the target metadata; the target metadata is one of heterogeneous metadata; obtaining target check rule information corresponding to the target metadata based on the database type and / or the project information; and checking the target metadata based on the target check rule information to obtain a check result. The scheme can accurately check the metadata based on the check rule of the database corresponding to the target metadata and / or the check rule of the project information, thereby avoiding the scheme of checking the heterogeneous metadata by using one set of check rules, and improving the check accuracy.
[0041] Embodiment Two
[0042] Figure 2 A flowchart of a heterogeneous metadata check method provided by Embodiment Two of the application is based on the above-described embodiments and is optimized.
[0043] It should be noted that when designing a database table metadata, the specifications of different types of databases can be inconsistent, for example, the field types, keywords, and operation functions of different types of databases can be different. Therefore, different specifications of database tables, fields, partitions, and subtable designs can be built in from the two dimensions of database performance and function according to different database types.
[0044] For example, for mainstream heterogeneous databases such as Oracle, MySQL, PostgreSQL, and Hive, the metadata specifications such as naming conventions, type mapping, and annotation requirements are preconfigured and structured.
[0045] As shown in Figure 2 The method of the embodiment of the application specifically comprises the following steps:
[0046] S210, obtaining target metadata, and determining a database type and / or project information of the target metadata; the target metadata is one of heterogeneous metadata.
[0047] S220, obtaining target check rule information corresponding to the target metadata based on the database type and / or the project information.
[0048] In this embodiment of the application, optionally, obtaining target metadata and determining the database type of the target metadata includes: obtaining target metadata of the database table during the database table design stage; determining the database type to which the database table belongs; and accordingly, obtaining target verification rule information corresponding to the target metadata based on the database type, including: obtaining target verification rule information from the pre-established verification rule information corresponding to each database type based on the database type.
[0049] For example, in one feasible solution, metadata can be validated in real time during the database table design phase. After obtaining the database table's metadata, the database type to which the database table belongs is determined. Based on the database type, target validation rule information is obtained from pre-established validation rule information corresponding to each database type. This target validation rule information corresponds to the validation information of the database type of the target metadata. This solution is configured in such a way that different database types correspond to different validation information, enabling precise validation of each metadata element in heterogeneous data.
[0050] In this embodiment of the application, optionally, obtaining target metadata and determining the database type of the target metadata includes: obtaining target metadata of the database table during the database table design stage; determining the project information corresponding to the target metadata; and accordingly, obtaining target verification rule information corresponding to the target metadata based on the project information, including: obtaining target verification rule information from the verification rule information corresponding to each pre-established project information based on the project information.
[0051] It should be noted that, in addition to the database table metadata design specifications, different project teams often have their own personalized internal design constraints and specifications, such as table names starting with specific rules, table field naming rules, and inconsistencies in common table fields. Therefore, different project design specifications should be set for different projects to more accurately verify the target metadata based on the project information corresponding to the target metadata.
[0052] For example, the project information may include: business domain, project team, compliance level, etc. Based on the above project information, a rule set specific to the project can be dynamically loaded, which can support hot updates and canary releases of rules, realize refined governance of "a thousand enterprises, a thousand faces", and avoid rule rigidity and resource waste.
[0053] In this embodiment of the application, optionally, obtaining target metadata and determining the database type and project information of the target metadata includes: obtaining target metadata of the database table during the database table design stage; determining the database type to which the database table belongs and the project information corresponding to the target metadata; correspondingly, obtaining target verification rule information corresponding to the target metadata based on the database type and project information includes: obtaining first target verification rule information from the pre-established verification rule information corresponding to each database type based on the database type; obtaining second target verification rule information from the pre-established verification rule information corresponding to each project information based on the project information; and integrating the first target verification rule information and the second target verification rule information to obtain target verification rule information.
[0054] For example, in a specific example, the corresponding metadata validation rule engine can be automatically adapted and loaded based on the database type and project selected by the user during design. The process is as follows: Figure 3 As shown.
[0055] In this embodiment of the application, optionally, the target verification rules corresponding to the database type include: database performance verification rules and database function verification rules.
[0056] For example, this solution incorporates different specifications for database tables, fields, partitions, and table sharding designs based on both performance and functionality for different database types. This configuration allows for comprehensive validation across both performance and functionality dimensions.
[0057] S230, the target metadata is verified based on the target verification rule information to obtain the verification result.
[0058] Optionally, in the verification process, the method further includes: inputting the field information of the target metadata and the pre-established knowledge base into the semantic recognition model to obtain the field design verification result of the metadata.
[0059] This solution is configured to use a semantic recognition model to identify field information, and then perform targeted validation based on that information, improving the depth and accuracy of the validation. For example, if the field information is a mobile phone number, it can be validated to see if it has 11 digits, etc.
[0060] For example, the technical solution of this application introduces a semantic understanding model, which can identify (such as "amount", "mobile phone number", "ID card" etc.) business keywords, and automatically determine whether the field design conforms to business logic and compliance requirements by combining industry knowledge base, significantly improving the verification depth.
[0061] In this embodiment of the application, optionally, the target metadata is verified based on the target verification rule information to obtain a verification result, including: performing architectural processing on the natural language rules in the target verification rule information to obtain executable verification rules; and verifying the target metadata based on the executable verification rules to obtain a verification result.
[0062] For example, in some scenarios that incorporate knowledge of specific business domains, the validation rules are expressed in natural language and cannot be directly validated. Therefore, this application embodiment constructs a structured rule expression to convert the natural language rules into executable logic before validation. For example, if the field name contains 'phone', then the type is string, and it conforms to the regular expression for mobile phone numbers and is not empty.
[0063] Optionally, in this embodiment of the application, the target metadata is verified based on the target verification rule information to obtain a verification result, including: if it is determined that there is verification abnormal data in the target metadata, the verification abnormal data and the associated information corresponding to the verification abnormal data are obtained so that the verification personnel can determine the verification result based on the associated information corresponding to the verification abnormal data.
[0064] For example, during metadata verification, rule conflicts, low confidence, or boundary scenarios are automatically marked as "to be reviewed" and a structured context (i.e., the associated information corresponding to the abnormal data, such as historical precedents, rule basis, similar field processing records, etc.) is pushed to assist in efficient human decision-making and break the dilemma of "fully automated is unreliable and fully manual is inefficient".
[0065] S240, Display the verification result of each verification item in the target metadata.
[0066] S250: For verification items with abnormal verification results, the cause of the abnormality is displayed, and repair suggestions are obtained from a pre-established verification abnormality information database and displayed.
[0067] For example, after validating the database table metadata, the validation results can be displayed in the corresponding position for each validation item. A green checkmark indicates compliance, a yellow exclamation mark indicates a warning (non-standard naming but acceptable), a red cross indicates validation failure, and gray indicates manual review is required. A "one-click repair" function is also provided, which automatically provides repair suggestions based on the reasons for the validation errors.
[0068] For example, after the verification results are generated, the problematic items are immediately highlighted on the modeling interface, and "one-click repair" suggestions are provided (such as completing comments or correcting types); at the same time, the manual review results are fed back to the rule base to drive the continuous optimization of rules, forming a self-evolving closed loop of "verification - feedback - repair - learning".
[0069] This technical solution achieves the following: Cross-database heterogeneity compatibility: It can adapt to metadata verification of multiple types of databases; This solution improves verification accuracy through dynamic governance of multi-tenant rules and flexible loading of exclusive specifications according to projects; This solution improves verification accuracy by using semantic-level intelligent verification, which goes beyond the grammatical level to understand business intent; This solution ensures no rule blind spots through human-machine collaboration; and It features real-time closed-loop design: Errors are detected, corrected, and prevented early. Overall, it forms a proactive, intelligent, and closed-loop metadata quality control system, significantly improving the enterprise's data governance level and database design standardization, and has outstanding practicality and innovation.
[0070] Example 3
[0071] Figure 4 This is a schematic diagram of a heterogeneous metadata verification device provided in Embodiment 3 of this application. This device can execute the heterogeneous metadata verification method provided in any embodiment of this invention, and possesses the corresponding functional modules and beneficial effects of the method execution. For example... Figure 4 As shown, the device includes:
[0072] The target metadata acquisition module 310 is used to acquire target metadata and determine the database type and / or project information of the target metadata; the target metadata is one of the metadata in heterogeneous metadata;
[0073] The target verification rule information determination module 320 is used to obtain the target verification rule information corresponding to the target metadata based on the database type and / or project information.
[0074] The verification module 330 is used to verify the target metadata based on the target verification rule information and obtain the verification result.
[0075] The technical solution of this application embodiment includes: a target metadata acquisition module 310, used to acquire target metadata and determine the database type and / or project information of the target metadata; the target metadata is metadata in heterogeneous metadata; a target verification rule information determination module 320, used to acquire target verification rule information corresponding to the target metadata based on the database type and / or project information; and a verification module 330, used to verify the target metadata based on the target verification rule information to obtain a verification result. This solution can accurately verify the metadata based on the verification rules of the database corresponding to the target metadata and / or the verification rules of the project information, thereby avoiding the need to use a single set of verification rules for heterogeneous metadata and improving verification accuracy.
[0076] Optionally, in this embodiment of the application, the target metadata acquisition module 310 includes:
[0077] The metadata acquisition unit is used to acquire the target metadata of the database table during the database table design phase.
[0078] A database type determination unit is used to determine the database type to which the database table belongs;
[0079] Correspondingly, the target verification rule information determination module 320 includes:
[0080] The target verification rule information determination unit is used to obtain target verification rule information from the pre-established verification rule information corresponding to each database type based on the database type.
[0081] In this embodiment of the application, optionally, the target verification rules corresponding to the database type include: database performance verification rules and database function verification rules.
[0082] Optionally, in this embodiment of the application, the device further includes:
[0083] The field design verification result determination unit is used to input the field information of the target metadata and the pre-established knowledge base into the semantic recognition model to obtain the field design verification result of the metadata.
[0084] Optionally, in this embodiment of the application, the verification module 330 includes:
[0085] The architecture processing unit is used to perform architecture processing on the natural language rules in the target verification rule information to obtain executable verification rules;
[0086] The verification result determination unit is used to verify the target metadata based on the executable verification rules and obtain the verification result.
[0087] Optionally, in this embodiment of the application, the verification module 330 includes:
[0088] An anomaly handling unit is used to, if it is determined that there is verification anomaly data in the target metadata, obtain the verification anomaly data and the associated information corresponding to the verification anomaly data, so that the verification personnel can determine the verification result based on the associated information corresponding to the verification anomaly data.
[0089] Optionally, in this embodiment of the application, the device further includes:
[0090] The verification result display module is used to display the verification result of each verification item in the target metadata;
[0091] The error reason display module is used to display the error reason for the verification item with an abnormal verification result and to obtain and display the repair suggestions from the pre-established verification error information database.
[0092] The heterogeneous metadata verification device provided in this application embodiment can execute the heterogeneous metadata verification method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.
[0093] Example 4
[0094] Figure 5 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.
[0095] like Figure 5 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0096] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0097] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as methods for verifying heterogeneous metadata.
[0098] In some embodiments, the heterogeneous metadata verification method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the heterogeneous metadata verification method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the heterogeneous metadata verification method by any other suitable means (e.g., by means of firmware).
[0099] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0100] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0101] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0102] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0103] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.
[0104] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.
[0105] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.
[0106] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. A method for verifying heterogeneous metadata, characterized in that, include: Obtain the target metadata and determine the database type and / or project information of the target metadata; The target metadata is one of the metadata in the heterogeneous metadata; Based on the database type and / or project information, obtain the target verification rule information corresponding to the target metadata; The target metadata is verified based on the target verification rule information to obtain the verification result.
2. The method according to claim 1, characterized in that, Obtain target metadata and determine the database type of the target metadata, including: During the database table design phase, obtain the target metadata of the database table; Determine the database type to which the database table belongs; Accordingly, based on the database type, the target verification rule information corresponding to the target metadata is obtained, including: Based on the database type, the target verification rule information is obtained from the pre-established verification rule information corresponding to each database type.
3. The method according to claim 1, characterized in that, The target verification rules corresponding to the database type include: database performance verification rules and database function verification rules.
4. The method according to claim 1, characterized in that, During the verification process, the method further includes: The target metadata field information and the pre-established knowledge base are input into the semantic recognition model to obtain the field design verification results of the metadata.
5. The method according to claim 1, characterized in that, The target metadata is validated based on the target validation rule information to obtain validation results, including: The natural language rules in the target verification rule information are structurally processed to obtain executable verification rules; The target metadata is validated based on the executable validation rules to obtain the validation result.
6. The method according to claim 1, characterized in that, The target metadata is validated based on the target validation rule information to obtain validation results, including: If it is determined that there is abnormal verification data in the target metadata, the abnormal verification data and the associated information corresponding to the abnormal verification data are obtained so that the verification personnel can determine the verification result based on the associated information corresponding to the abnormal verification data.
7. The method according to claim 1, characterized in that, After verifying the target metadata based on the target verification rule information and obtaining the verification result, the method further includes: Display the verification result of each verification item in the target metadata; For verification items with abnormal verification results, the cause of the abnormality is displayed, and repair suggestions are obtained from a pre-established verification abnormality information database and displayed.
8. A device for verifying heterogeneous metadata, characterized in that, include: The target metadata acquisition module is used to acquire target metadata and determine the database type and / or project information of the target metadata; The target metadata is one of the metadata in the heterogeneous metadata; The target verification rule information determination module is used to obtain the target verification rule information corresponding to the target metadata based on the database type and / or project information. The verification module is used to verify the target metadata based on the target verification rule information and obtain the verification result.
9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the heterogeneous metadata verification method according to any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method for verifying heterogeneous metadata as described in any one of claims 1-7.