Data task blood relationship construction method and device, equipment and storage medium
By establishing the data task lineage between data warehouse tasks and business domains, the problem of unclear task attribution in existing technologies is solved, enabling full-dimensional traceability from the technology chain to the business domain and improving data application efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-31
- Publication Date
- 2026-04-10
AI Technical Summary
The data lineage of existing data warehouse tasks is limited to the data warehouse task and the database, lacking external business domain information. This makes it impossible for task owners to trace the business line affiliation of tasks, resulting in low efficiency in business data application.
By obtaining the database call logs and configuration files of the product business system, the business domain is determined, and the target database is determined based on the database call logs, thus constructing the data task lineage between the target data warehouse task and the business domain.
It enables full-dimensional traceability of data warehouse tasks from the technical link to the business domain, enabling task owners to clearly understand the business line scope corresponding to the task and improving the efficiency of business data application.
Smart Images
Figure CN121836749A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data debugging technology, and more specifically, to a method, apparatus, device, and storage medium for constructing a data task lineage. Background Technology
[0002] In data debugging technology, the data warehouse, as the core data storage and transfer carrier, relies on a data lineage system for end-to-end traceability of data tasks. The correlation analysis of data entry, exit, and transformation is crucial for ensuring data reliability and supporting data management. Data lineage describes the dynamic network of relationships formed throughout the entire process of data generation, processing, transfer, and dissolution. Its core characteristics are reflected in four dimensions: attribution, multi-source nature, traceability, and hierarchy. Meanwhile, business domains (such as e-commerce transaction domains and payment settlement domains) are the core basis for business line division, and the precise correlation between data tasks and business domains is a fundamental requirement for achieving business-oriented data control.
[0003] The data lineage of existing data warehouse tasks is limited to the technical link between the data warehouse task and the database, lacking external domain information. As a result, the task owner cannot know which business line the task belongs to, and cannot trace the origin from the technical link to the business domain, leading to low efficiency in business data application.
[0004] How to establish the data task lineage between data warehouse tasks and business domains to achieve full-dimensional traceability of data warehouse tasks from the technical link to the business domain affiliation, so that task owners clearly know the business line scope to which the task belongs and improve the efficiency of business data application, is an issue that needs attention. Summary of the Invention
[0005] In view of the above problems, this application provides a method, apparatus, device and storage medium for constructing data task lineage, so as to realize the full-dimensional traceability of data warehouse tasks from the technical link to the business domain, so that the task owner clearly knows the business line scope corresponding to the task and improves the efficiency of business data application.
[0006] To achieve the above objectives, the following specific solutions are proposed:
[0007] A method for constructing data task lineage includes:
[0008] Obtain the database call logs and configuration files of the product business system;
[0009] Identify the business domains contained in the business system configuration file;
[0010] Based on the database call log, determine the first target database associated with the business domain;
[0011] Identify target data warehouse tasks that have a data lineage relationship with the first target database;
[0012] Establish the data task lineage between the target data warehouse task and the business domain.
[0013] Optionally, there are multiple product business systems, and each business system configuration file contains several business domains;
[0014] Based on the database call logs, the first target database associated with the business domain is determined, including:
[0015] For each business domain, a target business system configuration file corresponding to the business domain is determined. Based on the target product business system where the target business system configuration file is located, and by parsing the database call link log of the target product business system, a first target database associated with the business domain is obtained.
[0016] Optionally, establishing the data task lineage between the target data warehouse task and the business domain includes:
[0017] By integrating the business domain into the target data warehouse task, a data task lineage is established between the target data warehouse task and the business domain.
[0018] Optionally, the business domain is at least one;
[0019] The method also includes:
[0020] Construct a business domain database association table, wherein the business domain database association table contains information about each business domain and database information associated with each business domain;
[0021] From the existing data warehouse task lineage system, extract the second target database associated with each data warehouse task, wherein the data warehouse task lineage system contains data lineage information of multiple data warehouse tasks, and the data lineage information of each data warehouse task contains the second target database associated with that data warehouse task;
[0022] For each data warehouse task associated with the second target database, based on the business domain database association table, the target business domain associated with the second target database is determined. By integrating the target business domain into the data warehouse task, the data task lineage between the data warehouse task and the target business domain is constructed.
[0023] An apparatus for constructing data task lineage, comprising:
[0024] The acquisition unit is used to acquire the database call logs and configuration files of the product business system;
[0025] A business domain determination unit is used to determine the business domains contained in the business system configuration file.
[0026] The first target database determination unit is used to determine the first target database associated with the business domain based on the database call link log;
[0027] The target data warehouse task determination unit is used to determine target data warehouse tasks that have a data lineage relationship with the first target database.
[0028] The first data task lineage construction unit is used to construct the data task lineage between the target data warehouse task and the business domain.
[0029] Optionally, there are multiple product business systems, and each business system configuration file contains several business domains;
[0030] The first target database determination unit includes:
[0031] The first target database determination subunit is used to determine the target business system configuration file corresponding to each business domain, and obtain the first target database associated with the business domain by parsing the database call link log of the target product business system in which the target business system configuration file is located.
[0032] Optionally, the first data task lineage building unit includes:
[0033] The first data task lineage construction subunit is used to construct the data task lineage between the target data warehouse task and the business domain by integrating the business domain into the target data warehouse task.
[0034] Optionally, the business domain is at least one;
[0035] The device also includes:
[0036] The association table construction unit is used to construct a business domain database association table, wherein the business domain database association table contains information about each business domain and database information associated with each business domain;
[0037] The second target database extraction unit is used to extract the second target database associated with each data warehouse task from the existing data warehouse task lineage system, wherein the data warehouse task lineage system contains data lineage information of multiple data warehouse tasks, and the data lineage information of each data warehouse task contains the second target database associated with that data warehouse task.
[0038] The second data task lineage construction unit is used to determine the target business domain associated with the second target database for each data warehouse task based on the business domain database association table, and to construct the data task lineage between the data warehouse task and the target business domain by integrating the target business domain into the data warehouse task.
[0039] A data task lineage building device, including a memory and a processor;
[0040] The memory is used to store programs;
[0041] The processor is used to execute the program to implement the various steps of the data task lineage construction method described above.
[0042] A storage medium having a computer program stored thereon, which, when executed by a processor, implements the various steps of the method for constructing a data task lineage as described above.
[0043] By employing the above technical solution, this application obtains the database call chain logs and configuration files of the product business system, determines the business domains contained in the configuration files, identifies the first target database associated with the business domain based on the database call chain logs, identifies the target data warehouse task with a data lineage relationship to the first target database, and constructs the data task lineage between the target data warehouse task and the business domain. Thus, by constructing the association between the database and the business domain, and then reverse-matching the corresponding business domain from the database with a data lineage relationship to the data warehouse task, a full-dimensional traceability of the data warehouse task from the technical chain to the business domain affiliation is achieved. This allows the task owner to clearly understand the business line scope corresponding to the task, improving the efficiency of business data application. Attached Figure Description
[0044] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:
[0045] Figure 1 This is a schematic diagram illustrating a process for constructing a data task lineage, as provided in an embodiment of this application.
[0046] Figure 2 A schematic diagram of a device structure for implementing data task lineage construction is provided in an embodiment of this application;
[0047] Figure 3This is a schematic diagram of the structure of a device for implementing data task lineage construction, provided in an embodiment of this application. Detailed Implementation
[0048] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0049] The proposed solution can be implemented based on a terminal with data processing capabilities, such as a computer, cloud, or server.
[0050] Next, combined Figure 1 The method for constructing the data task lineage of this application may include the following steps:
[0051] Step S110: Obtain the database call logs and configuration files of the product business system.
[0052] Specifically, the database call chain log can represent a structured log recording cross-module and cross-node database call behavior of the product business system. The database call chain log can contain key information such as the call initiator, target database, data interaction path, and related table fields. The business system configuration file can represent the preset static configuration document of the product business system, containing structured information such as business domain division rules, module function definitions, and data flow specifications.
[0053] Understandably, database call logs provide the actual interaction traces between business operations and the database, ensuring the objectivity of the relationships; business system configuration files clearly define the standard definitions of business domains, ensuring the accuracy of business domain identification.
[0054] Step S120: Determine the business domains contained in the business system configuration file.
[0055] Specifically, the structured format of the business system configuration file can be parsed first, such as XML, JSON and other preset formats, to identify the key fields that mark the business domain definition, such as "business domain name", "business domain code", "module", "data permission scope" etc.; then, complete business domain information can be extracted based on the field information, invalid and duplicate configuration items can be excluded, and the completeness of the business domain definition can be verified; finally, a standardized business domain list can be formed to clarify the unique identifier and core attributes of each business domain.
[0056] Step S130: Based on the database call link log, determine the first target database associated with the business domain.
[0057] Specifically, the database call logs can be structured and parsed first to extract key information such as the calling module, target database address, data interaction table name, field mapping relationships, and call context characteristics. Then, based on the standardized business domain list compiled in step S120, a correspondence between business domains and system functional modules can be established. Irrelevant and redundant call records in the logs are filtered out, retaining valid database calls initiated by the functional modules belonging to the business domains. Next, by matching the mapping relationship between the calling module identifier and the business domain, the databases pointed to by these calls are matched, and core information such as database name, instance address, and associated business tables are extracted. Finally, the matching results are cross-validated, and databases with accidental associations are excluded based on indicators such as call frequency and data interaction stability. Ultimately, the primary target database with a stable and direct association with each business domain is determined, ensuring the accuracy and reliability of the association relationships.
[0058] Step S140: Determine the target data warehouse task that has a data lineage relationship with the first target database.
[0059] Specifically, the process begins by retrieving the full information of the existing data lineage system in the data warehouse. This lineage system can encompass all data warehouse tasks, which can be data inbound, outbound, or transformation tasks across the entire data chain. It includes core information such as data source information, target data storage address, field flow mapping rules, and task dependencies. Then, the key identifiers (including database name, core business table name, and feature fields) of the first target database determined in step S130 are extracted. This serves as the core basis for matching and retrieval. The lineage of all data warehouse tasks is traversed. This can be done through data source matching (e.g., tasks reading tables / fields from the first target database), target data matching (e.g., tasks outputting data to tables related to the first target database), and intermediate data flow matching (e.g., tasks indirectly related to the first target database through intermediate or temporary tables). These multi-dimensional retrieval methods filter out data warehouse tasks with direct or indirect data lineage relationships. Finally, the filtering results are verified for lineage integrity. Tasks with only momentary data interaction and no continuous lineage relationship are excluded, while target data warehouse tasks with a clear lineage relationship to the first target database and close business relevance are identified.
[0060] Step S150: Construct the data task lineage between the target data warehouse task and the business domain.
[0061] Specifically, the core components of the data task lineage can be clearly defined first, including the unique identifier of the target data warehouse task, the standardized label of the corresponding business domain, the basis for association, and the complete lineage link (the data flow path from business domain → first target database → data warehouse task). The method for constructing the data task lineage between the target data warehouse task and the business domain can be to integrate business domain information as a core attribute into the existing data warehouse task lineage system, add a unique business domain label to each target data warehouse task, thereby establishing a two-way mapping relationship between task identifier and business domain label, and generating a standardized data warehouse task-business domain lineage dictionary. This dictionary clearly records the association logic, effective time, and update logs of each task and business domain, achieving full-dimensional traceability of data warehouse tasks from the technical flow to the business scope.
[0062] The data task lineage construction method provided in this embodiment obtains the database call link logs and configuration files of the product business system, determines the business domains contained in the configuration files, identifies a first target database associated with the business domain based on the database call link logs, identifies target data warehouse tasks with data lineage relationships with the first target database, and constructs the data task lineage between the target data warehouse tasks and the business domains. Therefore, by constructing the association between databases and business domains, and then reverse-matching the corresponding business domains from databases with data lineage relationships to data warehouse tasks, a full-dimensional traceability of data warehouse tasks from the technical link to their business domain affiliation is achieved. This allows task owners to clearly understand the business line scope corresponding to their tasks, improving the efficiency of business data application.
[0063] In some embodiments of this application, the commodity business system mentioned in the foregoing embodiments is further described. Specifically, there can be multiple commodity business systems, and the core business domains (such as transactions, payments, logistics, etc.) belong to different systems. The core databases and table structures, functional modules, and other features have different focuses. The data interaction objects and call chain characteristics of different commodity business systems also differ to adapt to different business scenarios. Since a commodity business system has its own focused business domains and its own unfocused business domains, the business system configuration file of a commodity business system can contain several business domains.
[0064] Based on this, the process of determining the first target database associated with the business domain based on the database call link log in step S130 above will be described. This process may include:
[0065] For each business domain, a target business system configuration file corresponding to the business domain is determined. Based on the target product business system where the target business system configuration file is located, and by parsing the database call link log of the target product business system, a first target database associated with the business domain is obtained.
[0066] Understandably, using business domains as indexes, and then corresponding to specific target product business systems, avoids interference from business domains with the same name and overlapping data across different systems. By parsing the specific logs of this system, the databases directly related to the business domain can be accurately located, eliminating erroneous associations with unrelated systems and thus preventing cross-system mismatches. For the target product business system corresponding to the business domain, it is unnecessary to traverse the massive logs of all product business systems; only the logs of the target product business system need to be parsed, significantly reducing the amount of data processing, shortening the time spent on link analysis, reducing resource consumption, and improving the overall process execution efficiency.
[0067] In some embodiments of this application, the process of step S150 above, which involves constructing the data task lineage between the target data warehouse task and the business domain, is described. This process may include:
[0068] By integrating the business domain into the target data warehouse task, a data task lineage is established between the target data warehouse task and the business domain.
[0069] Specifically, standardized business domain information, including business domain name, unique code, core attributes, and the business scenario to which it belongs, can be deeply integrated into the target data warehouse task. Specifically, it can be embedded into the existing task lineage system of the data warehouse in the form of business domain tags, binding a unique business domain identifier to each target data warehouse task, and at the same time as associating the core basis of the integration process: the corresponding first target database information, the key index of the database call link log, and the matching record of the business system configuration file.
[0070] It is understandable that by using business domain attributes as the core metadata of data warehouse tasks, and complementing the original technical link information of the tasks, a complete association link is constructed between the business domain, the first target database, and the target data warehouse task. This ensures that the data task lineage retains the technical flow trajectory and clarifies the business affiliation, ultimately forming a data task lineage that combines technical integrity and business readability, and enabling full-dimensional traceability from business scenarios to data warehouse tasks.
[0071] In some embodiments of this application, a data task lineage construction scheme can be carried out from the perspective of data warehouse tasks. Based on this, the data task lineage construction method provided by this application may further include:
[0072] S1. Construct a database relationship table for the business domain.
[0073] The business domain database association table contains information about each business domain and database information associated with each business domain.
[0074] Understandably, the business domain database relationship table integrates the business domain and database relationship logic scattered across various product business systems into a structured, unified information carrier. It clearly records the complete information of each business domain and the core identifier of its corresponding database, avoiding matching chaos caused by fragmented information and inconsistent formats. In subsequent processes, there's no need to repeatedly parse business system configuration files and database call logs; target information can be retrieved directly and quickly, significantly reducing redundant data processing, lowering resource consumption, and supporting cross-scenario reuse to adapt to the business domain relationship requirements of multiple batches of data warehouse tasks. Furthermore, the business domain database relationship table, having undergone multi-dimensional verification in the early stages, establishes stable relationships, avoiding erroneous matching caused by instantaneous calls and cross-system interference. It also facilitates subsequent dynamic updates; when business domain divisions or database configurations change, only the information in the table needs to be updated to synchronously adapt to the entire process, ensuring that the relationships remain accurate and effective.
[0075] S2. Extract the second target database associated with each data warehouse task from the existing data warehouse task lineage system.
[0076] The data warehouse task lineage system includes data lineage information for multiple data warehouse tasks, and the data lineage information for each data warehouse task includes the second target database associated with that data warehouse task.
[0077] S3. For each data warehouse task associated with the second target database, based on the business domain database association table, determine the target business domain associated with the second target database, and integrate the target business domain into the data warehouse task to construct the data task lineage between the data warehouse task and the target business domain.
[0078] Understandably, constructing a data task lineage from the perspective of data warehouse tasks allows us to start with the existing data warehouse task lineage system and extract the associated second target database for each data warehouse task. This ensures comprehensive coverage of all data warehouse tasks, avoiding the potential omission of peripheral or indirectly related tasks that might occur when starting from the business system side, thus guaranteeing the integrity of business domain associations. Matching based on the business domain database association table eliminates the need to repeatedly parse massive amounts of business system configuration files and call logs. It directly and quickly locates the target business domain through the second target database, significantly reducing data processing volume and resource consumption. Furthermore, the stable mapping relationship of the association table avoids the risk of mismatches caused by cross-system or instantaneous calls, improving the accuracy of binding business domains to data warehouse tasks. Based on the business domain database association table, reverse matching of the databases directly links the business affiliation of each data warehouse task to its associated second target database, forming a clear traceability link from data warehouse task to second target database to target business domain. This preserves the integrity of the original technical lineage and clarifies business affiliation.
[0079] The apparatus for constructing data task lineages provided in the embodiments of this application will be described below. The apparatus for constructing data task lineages described below can be referred to in correspondence with the method for constructing data task lineages described above.
[0080] See Figure 2 , Figure 2 This is a schematic diagram of a device structure for implementing data task lineage construction disclosed in an embodiment of this application.
[0081] like Figure 2 As shown, the device may include:
[0082] Acquisition unit 11 is used to acquire the database call chain logs and business system configuration files of the product business system;
[0083] The business domain determination unit 12 is used to determine the business domains contained in the business system configuration file;
[0084] The first target database determination unit 13 is used to determine the first target database associated with the business domain based on the database call link log;
[0085] The target data warehouse task determination unit 14 is used to determine target data warehouse tasks that have a data lineage relationship with the first target database.
[0086] The first data task lineage building unit 15 is used to build the data task lineage between the target data warehouse task and the business domain.
[0087] Optionally, there are multiple product business systems, and each business system configuration file contains several business domains;
[0088] The first target database determination unit includes:
[0089] The first target database determination subunit is used to determine the target business system configuration file corresponding to each business domain, and obtain the first target database associated with the business domain by parsing the database call link log of the target product business system in which the target business system configuration file is located.
[0090] Optionally, the first data task lineage building unit includes:
[0091] The first data task lineage construction subunit is used to construct the data task lineage between the target data warehouse task and the business domain by integrating the business domain into the target data warehouse task.
[0092] Optionally, the business domain is at least one;
[0093] The device also includes:
[0094] The association table construction unit is used to construct a business domain database association table, wherein the business domain database association table contains information about each business domain and database information associated with each business domain;
[0095] The second target database extraction unit is used to extract the second target database associated with each data warehouse task from the existing data warehouse task lineage system, wherein the data warehouse task lineage system contains data lineage information of multiple data warehouse tasks, and the data lineage information of each data warehouse task contains the second target database associated with that data warehouse task.
[0096] The second data task lineage construction unit is used to determine the target business domain associated with the second target database for each data warehouse task based on the business domain database association table, and to construct the data task lineage between the data warehouse task and the target business domain by integrating the target business domain into the data warehouse task.
[0097] The data task lineage construction apparatus provided in this application embodiment can be applied to devices for data task lineage construction, such as terminals: mobile phones, computers, etc. Optionally, Figure 3 The diagram shows the hardware structure of the device for building the data task lineage, with reference to... Figure 3 The hardware structure of a device built on the data task lineage may include: at least one processor 1, at least one communication interface 2, at least one memory 3, and at least one communication bus 4;
[0098] In this embodiment of the application, the number of processor 1, communication interface 2, memory 3, and communication bus 4 is at least one, and processor 1, communication interface 2, and memory 3 communicate with each other through communication bus 4;
[0099] Processor 1 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.
[0100] Memory 3 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device;
[0101] The memory stores a program, which the processor can call. The program is used for:
[0102] Obtain the database call logs and configuration files of the product business system;
[0103] Identify the business domains contained in the business system configuration file;
[0104] Based on the database call log, determine the first target database associated with the business domain;
[0105] Identify target data warehouse tasks that have a data lineage relationship with the first target database;
[0106] Establish the data task lineage between the target data warehouse task and the business domain.
[0107] Optionally, the refined and extended functions of the program can be found in the description above.
[0108] This application embodiment also provides a storage medium that can store a program suitable for execution by a processor, the program being used for:
[0109] Obtain the database call logs and configuration files of the product business system;
[0110] Identify the business domains contained in the business system configuration file;
[0111] Based on the database call log, determine the first target database associated with the business domain;
[0112] Identify target data warehouse tasks that have a data lineage relationship with the first target database;
[0113] Establish the data task lineage between the target data warehouse task and the business domain.
[0114] Optionally, the refined and extended functions of the program can be found in the description above.
[0115] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0116] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referred to each other.
[0117] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for constructing data task lineage, characterized in that, include: Obtain the database call logs and configuration files of the product business system; Identify the business domains contained in the business system configuration file; Based on the database call log, determine the first target database associated with the business domain; Identify target data warehouse tasks that have a data lineage relationship with the first target database; Establish the data task lineage between the target data warehouse task and the business domain.
2. The method according to claim 1, characterized in that, There are multiple product business systems, and each business system configuration file contains several business domains; Based on the database call logs, the first target database associated with the business domain is determined, including: For each business domain, a target business system configuration file corresponding to the business domain is determined. Based on the target product business system where the target business system configuration file is located, and by parsing the database call link log of the target product business system, a first target database associated with the business domain is obtained.
3. The method according to claim 1, characterized in that, Constructing the data task lineage between the target data warehouse task and the business domain includes: By integrating the business domain into the target data warehouse task, a data task lineage is established between the target data warehouse task and the business domain.
4. The method according to any one of claims 1-3, characterized in that, The business domain is at least one; The method also includes: Construct a business domain database association table, wherein the business domain database association table contains information about each business domain and database information associated with each business domain; From the existing data warehouse task lineage system, extract the second target database associated with each data warehouse task, wherein the data warehouse task lineage system contains data lineage information of multiple data warehouse tasks, and the data lineage information of each data warehouse task contains the second target database associated with that data warehouse task; For each data warehouse task associated with the second target database, based on the business domain database association table, the target business domain associated with the second target database is determined. By integrating the target business domain into the data warehouse task, the data task lineage between the data warehouse task and the target business domain is constructed.
5. A device for constructing data task lineage, characterized in that, include: The acquisition unit is used to acquire the database call logs and configuration files of the product business system; A business domain determination unit is used to determine the business domains contained in the business system configuration file. The first target database determination unit is used to determine the first target database associated with the business domain based on the database call link log; The target data warehouse task determination unit is used to determine target data warehouse tasks that have a data lineage relationship with the first target database. The first data task lineage construction unit is used to construct the data task lineage between the target data warehouse task and the business domain.
6. The apparatus according to claim 5, characterized in that, There are multiple product business systems, and each business system configuration file contains several business domains; The first target database determination unit includes: The first target database determination subunit is used to determine the target business system configuration file corresponding to each business domain, and obtain the first target database associated with the business domain by parsing the database call link log of the target product business system in which the target business system configuration file is located.
7. The apparatus according to claim 5, characterized in that, The first data task lineage construction unit includes: The first data task lineage construction subunit is used to construct the data task lineage between the target data warehouse task and the business domain by integrating the business domain into the target data warehouse task.
8. The apparatus according to any one of claims 5-7, characterized in that, The business domain is at least one; The device also includes: The association table construction unit is used to construct a business domain database association table, wherein the business domain database association table contains information about each business domain and database information associated with each business domain; The second target database extraction unit is used to extract the second target database associated with each data warehouse task from the existing data warehouse task lineage system, wherein the data warehouse task lineage system contains data lineage information of multiple data warehouse tasks, and the data lineage information of each data warehouse task contains the second target database associated with that data warehouse task. The second data task lineage construction unit is used to determine the target business domain associated with the second target database for each data warehouse task based on the business domain database association table, and to construct the data task lineage between the data warehouse task and the target business domain by integrating the target business domain into the data warehouse task.
9. A device for constructing data task lineage, characterized in that, Including memory and processor; The memory is used to store programs; The processor is configured to execute the program to implement the various steps of the data task lineage construction method as described in any one of claims 1-4.
10. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method for constructing data task lineage as described in any one of claims 1-4.