A data link management method, device, equipment, medium, product

Abstract

The present application discloses a data link management method, apparatus, device, medium, and product, the method comprising: for any data link, when the data link comprises a first node and some nodes located upstream of the first node, such as a second node, if a data risk reporting request triggered for a first field in the first node is detected, field-level lineage tracing processing is first performed based on the field identifier carried by the data risk reporting request to obtain a processing result, so that the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node; then the first information is annotated on the task corresponding to the second field, and the second information is sent to the terminal corresponding to the second node, so that the terminal corresponding to the second node is used to display the second information, which is conducive to improving the impact assessment effect.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data link management method, device, equipment, medium, and product. Background Art

[0002] In some scenarios, such as data lakes and / or data warehouses, the processes of data generation, transfer, and processing create a link relationship between different data (or different tasks, or different data tables). This link relationship is used to describe the dependency relationship between different data (or different tasks, or different data tables), also known as the blood relationship. For ease of understanding, the following example is used to illustrate.

[0003] As an example, when node A in a certain scenario is used to generate and store data 1; node B is used to process data 1 to obtain and store data 2; node C is used to process data 2 to obtain and store data 3; and node D is used to process data 3 to obtain and store data 4, the data link in this scenario may at least include the link of node A→node B→node C→node D. Among them, there is the following positional relationship between these nodes: node A is located upstream of node B, node B, node C and node D are all located downstream of node A, node A and node B are both located upstream of node C, node D is located downstream of node C, and node A, node B, and node C are all located upstream of node D.

[0004] However, because the data links in some scenarios are relatively long, the data dependencies in these scenarios are relatively complex, making it difficult to evaluate the impact when data changes (or task changes, or data table changes) or failures occur, which in turn affects the effectiveness of data link management. Summary of the invention

[0005] In order to solve the above technical problems, the present application provides a data link management method, device, equipment, medium, and product.

[0006] In order to achieve the above objectives, the technical solutions provided by this application are as follows:

[0007] The present application provides a data link management method, the method comprising:

[0008] receiving a data risk reporting request triggered for a first field in a first node, the data risk reporting request being used to indicate a risk type and a risk level of the first field, and a field identifier carried by the data risk reporting request being used to identify the first field;

[0009] Perform field-level lineage tracing processing according to the field identifier to obtain a processing result, wherein the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node, and the second node is located upstream of the first node;

[0010] The first information is marked on the task corresponding to the second field, and the second information is sent to the terminal corresponding to the second node. The terminal corresponding to the second node is used to display the second information. The first information includes the risk type. The second information is determined based on part or all of the information carried by the data risk reporting request.

[0011] In a possible implementation manner, the task corresponding to the second field includes multiple tasks;

[0012] The path length between a target task among the multiple tasks and a task corresponding to the first field is not greater than the path length between any other task among the multiple tasks except the target task and the task corresponding to the first field;

[0013] The processing result is specifically used to indicate that: there is a blood relationship between the task corresponding to the first field in the first node and the target task;

[0014] The marking of the first information on the task corresponding to the second field includes:

[0015] The target task is labeled with first information.

[0016] In a possible implementation manner, after obtaining the processing result, the method further includes:

[0017] The second field in the data table of the second node is marked with third information, where the third information includes the risk type.

[0018] In a possible implementation manner, the second information is further determined based on at least one item of information of the second node;

[0019] The at least one item of information includes at least one of an identifier of a manager of the second node, an identifier of the second field, and an identifier of a data table to which the second field belongs.

[0020] The present application provides a data link management method, the method comprising:

[0021] receiving an impact determination request triggered for a target object in a second node, the impact determination request being used to request determination of a node affected by the target object, the object identifier carried in the impact determination request being used to identify the target object, the target object including at least one field in the second node; a risk declaration processing procedure of at least one first node located downstream of the second node having been executed, the risk declaration processing procedure being implemented using the above data link management method;

[0022] Performing query processing according to the at least one first node and the object identifier to obtain a query result, wherein the query result is used to indicate that one or more first nodes are affected by the target object;

[0023] Feedback is provided to the impact determination request based on the query result.

[0024] In a possible implementation manner, the method is applied to a terminal corresponding to the second node,

[0025] Before receiving the impact determination request triggered on the target object in the second node, the method further includes:

[0026] Displaying a declaration information list and a query box on the terminal, the declaration information list including risk declaration information corresponding to the at least one first node;

[0027] The receiving an impact determination request triggered on a target object in a second node includes:

[0028] receiving an identifier of the target object input into the query box;

[0029] The query processing is performed according to the at least one first node and the object identifier to obtain a query result, including:

[0030] According to the object identifier, query the declaration information list to obtain a query result, wherein the query result is used to indicate the risk declaration information matching the object identifier;

[0031] The providing feedback on the impact determination request according to the query result includes:

[0032] Based on the query result, the display content on the terminal is updated, and the updated display content is used to indicate the risk declaration information matching the object identifier.

[0033] In one possible implementation manner, the at least one first node includes a target node;

[0034] The query result is used to indicate that the target node is affected by the target object;

[0035] After obtaining the query result, the method further includes:

[0036] First prompt information is sent to the target node, where the first prompt information is used to indicate that the target node is affected by the target object in the second node.

[0037] In a possible implementation manner, the second node is used to perform change processing on the target object;

[0038] or,

[0039] The target object in the second node is obtained by locating a fault occurring in the third node, and the second node is located upstream of the third node.

[0040] In a possible implementation manner, the second node is used to perform change processing on the target object;

[0041] The method further comprises:

[0042] A second prompt message is sent to a fourth node, where the second prompt message is used to instruct a target object in the second node to undergo a change process, the fourth node being located downstream of the second node, and the fourth node is adjacent to the second node.

[0043] The present application provides a data link management device, comprising:

[0044] A first receiving unit, configured to receive a data risk reporting request triggered for a first field in a first node, wherein the data risk reporting request is used to indicate a risk type and a risk level of the first field, and a field identifier carried by the data risk reporting request is used to identify the first field;

[0045] a first processing unit, configured to perform field-level lineage tracing processing according to the field identifier to obtain a processing result, wherein the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node, and the second node is located upstream of the first node;

[0046] A first feedback unit is used to mark first information on the task corresponding to the second field, and to send second information to a terminal corresponding to the second node, wherein the terminal corresponding to the second node is used to display the second information, wherein the first information includes the risk type, and the second information is determined based on part or all of the information carried by the data risk reporting request.

[0047] The present application adopts a data link management device, comprising:

[0048] A second receiving unit is configured to receive an impact determination request triggered for a target object in a second node, the impact determination request is used to request determination of a node affected by the target object, the object identifier carried by the impact determination request is used to identify the target object, and the target object includes at least one field in the second node; a risk declaration processing process of at least one first node located downstream of the second node has been executed, and the risk declaration processing process is implemented by using the above data link management method;

[0049] A second processing unit, configured to perform query processing according to the at least one first node and the object identifier to obtain a query result, wherein the query result is used to indicate that one or more first nodes are affected by the target object;

[0050] The second feedback unit is used to provide feedback on the impact determination request according to the query result.

[0051] The present application provides an electronic device, the device comprising: a processor and a memory;

[0052] The memory is used to store instructions or computer programs;

[0053] The processor is used to execute the instructions or computer programs in the memory so that the electronic device executes the data link management method provided in the present application.

[0054] The present application provides a computer-readable medium, in which instructions or computer programs are stored. When the instructions or computer programs are executed on a device, the device executes the data link management method provided by the present application.

[0055] The present application provides a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program codes for executing the data link management method provided by the present application.

[0056] Compared with the related art, this application has at least the following advantages:

[0057] In the technical solution provided by the present application, for any data link, when the data link includes a first node and some nodes located upstream of the first node, such as a second node, if a data risk reporting request triggered for a first field in the first node is detected, field-level lineage tracing processing is first performed based on the field identifier carried by the data risk reporting request to obtain a processing result, so that the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node; then the first information is annotated on the task corresponding to the second field, and the second information is sent to the terminal corresponding to the second node, so that the terminal corresponding to the second node is used to display the second information.

[0058] Among them, because the first information includes the risk type carried by the data risk reporting request, after the first information is marked for the task corresponding to the second field, the second node or the manager of the second node can learn from the marked content of the task that when an error occurs in the task or the task is changed, it may cause risks to the first node, thereby determining that when an error occurs in the task or the task is changed, it may have an impact on the first node, such as a high-risk impact. In this way, it is possible to quickly determine the impact of the task when changes are made or failures occur with the help of the marked content, which is beneficial to improving the efficiency of impact determination, and further beneficial to improving the data link management effect.

[0059] In addition, because the second information is determined based on part or all of the information carried by the data risk reporting request, the second information can better indicate that when some objects in the second node, such as tasks, fields, data tables, etc., have errors or changes, they can affect the first node, so that the second information can more accurately indicate the impact of the second node on the first node, such as high-risk impact, and thus enable the manager of the second node to learn from the second information the impact of the second node on the first node, so that when the object fails or changes subsequently, the impact of the object can be quickly determined from the second information, which is beneficial to improving the efficiency of impact determination and thus beneficial to improving the data link management effect.

[0060] Based on the above three paragraphs, it can be seen that for any data link, the downstream node in the data link can inform its upstream node of its risky fields through declaration, so that the upstream node can accurately and timely know that when some fields, tasks or data tables in the upstream node are changed (or errors occur), it will cause risks to the downstream node. This is conducive to achieving efficient, accurate, and comprehensive impact assessment, thereby reducing failures, such as reducing failures caused by the upstream node's inability to perceive the risks involved in the downstream node to 0, which is conducive to improving the data link management effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0062] Figure 1 A flow chart of a data link management method provided in an embodiment of the present application;

[0063] Figure 2 A flow chart of a data link management method provided in an embodiment of the present application;

[0064] Figure 3 A schematic diagram of the structure of a data link management device provided in an embodiment of the present application;

[0065] Figure 4 A schematic diagram of the structure of a data link management device provided in an embodiment of the present application;

[0066] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0067] Research has found that for the data links in some related solutions, the upstream nodes in the data link cannot perceive the relevant information of the downstream nodes, such as high-risk fields, so that there is an information gap between the upstream nodes and the downstream nodes in the data link. As a result, when certain objects in the upstream nodes, such as data, tasks or data tables, are changed or errors occur, it will cause risks to the downstream nodes, which in turn causes these solutions to fail more frequently, especially those caused by unawareness of risks.

[0068] The study also found that for a data link, it may involve field-level lineage, task-level lineage, and data table-level lineage. Among them, because a task may involve one or more fields, the granularity of the task-level lineage is greater than the granularity of the field-level lineage, so that the information obtained by the lineage tracing process based on the task-level lineage is less than the information obtained by the lineage tracing process based on the field-level lineage, and thus the effect of the solution based on the task-level lineage is not as good as the effect of the solution based on the field-level lineage. Similarly, because a data table includes one or more fields, the granularity of the data table-level lineage is greater than the granularity of the field-level lineage, so that the information obtained by the lineage tracing process based on the data table-level lineage is less than the information obtained by the lineage tracing process based on the field-level lineage, and thus the effect of the solution based on the data table-level lineage is not as good as the effect of the solution based on the field-level lineage.

[0069] Based on the above research, in order to better improve the efficiency of impact assessment, the present application provides a solution, in which, for any data link, the downstream node in the data link can inform its upstream node of its risky fields through declaration, so that the upstream node can accurately and timely know that when some fields, tasks or data tables in the upstream node are changed (or errors occur), it will cause risks to the downstream node. This is conducive to achieving efficient, accurate, and comprehensive impact assessment, thereby reducing failures, such as reducing failures caused by the upstream node's inability to perceive the risks involved in the downstream node to 0, which is conducive to improving the data link management effect.

[0070] In addition, the present application does not limit the execution subject of the data link management method provided in the embodiment of the present application. For example, the data link management method provided in the embodiment of the present application can be applied to a terminal device or a server. For another example, the data link management method provided in the embodiment of the present application can also be implemented with the help of the data interaction process between the terminal device and the server. Among them, the terminal device can be a smart phone, a computer, a personal digital assistant (PDA), a tablet computer, etc. The server can be a stand-alone server, a cluster server or a cloud server.

[0071] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0072] In order to better understand the technical solution provided by the present application, the data link management method provided by the present application is described below with reference to some drawings. Figure 1 As shown, the data link management method provided in the embodiment of the present application includes the following S101-S103. Figure 1 A flowchart of a data link management method provided in an embodiment of the present application.

[0073] S101: Receive a data risk reporting request triggered for a first field in a first node, where the data risk reporting request is used to indicate a risk type and a risk level of the first field, and a field identifier carried by the data risk reporting request is used to identify the first field.

[0074] The first node refers to a node located downstream in a data link, such as a leaf node. For example, when the data link includes a link of node A→node B→node C→node D, the first node may be node D.

[0075] It should be noted that, for any node in a data link, the node may include at least some data tables and some tasks; and if there is no node upstream of the node in the data link, the node is a data generation node; but if there is a node upstream of the node in the data link, the data table in the node may be obtained by processing the data table in the node upstream of it.

[0076] The first field refers to a field that exists in the first node and can cause risks, such as high risks, so that the first field satisfies the following constraint: when an error occurs in the first field, a risk will occur, such as a high risk. For example, when the first node includes data table 4, and field 4 exists in the data table, if an error occurs in field 4, it will cause some risk, such as asset loss or customer complaints, etc., then field 4 can be regarded as the first field, so that the risk of field 4 can be notified to each node upstream of the first node in the future.

[0077] The data risk declaration request is used at least to transmit field-level risk information, such as the risk type and risk level of the first field in the first node, to each node upstream of the first node. It can be seen that in one possible implementation, the data risk declaration request can be used to indicate the risk type and risk level of the first field.

[0078] It should be noted that the present application does not limit the risk type. For example, the risk type may include asset loss or customer complaints. In addition, the present application does not limit the risk level. For example, for the risk type of asset loss, the level corresponding to the risk type may be divided according to the range of lost assets, so that the level may include: 0-150,000, 150,000-250,000, 250,000-500,000, 500,000-1 million, and more than 1 million. For another example, for the risk of customer complaints, the level corresponding to the risk type may be divided according to the number of complainants, so that the level may include: 1-99 people, 100-499 people, 500-999 people, and more than 1,000 people.

[0079] In addition, in some scenarios, in order to better overcome the defects caused by the lack of information communication between upstream and downstream, the present application also provides a possible implementation method of the above-mentioned data risk reporting request. In this method, the data risk reporting request may carry some configuration information of the first field, such as field identification, data quality requirements, data usage scenarios, risk type, risk level and other configuration information, so that the data risk reporting request can better express the characteristics of the first field, such as data quality requirements, data usage scenarios, risk type, risk level and other characteristics, so that these configuration information can be subsequently transmitted to each node located upstream of the first node with the help of the data risk reporting request, so that these upstream nodes can perceive the risk.

[0080] It should be noted that for the above paragraph, the field identifier is used to uniquely identify the first field, and this application does not limit the field identifier. For example, it can be implemented using the name of the first field. Data quality requirements refer to requirements that are pre-configured for the first field and must be met to avoid errors in the first field, such as table non-empty, table row fluctuations, primary key uniqueness, and some constraint configurations for the first field. The data usage scenario is pre-configured for the first field and is used to describe the scenario in which the first field is used.

[0081] Based on the above two paragraphs, it can be seen that in one possible implementation, the data risk declaration request carries at least a field identifier. The field identifier is used to identify the first field, so that other objects that have a blood relationship with the first field can be traced back based on the field identifier, such as fields, tasks, data tables, and other objects.

[0082] In addition, this application does not limit the triggering method of the above data risk reporting request. For ease of understanding, the following is an explanation combining two situations.

[0083] Case 1: When the first node is a leaf node, such as node D, and the task corresponding to the first field in the first node can be used by the fifth node, such as node E, if the fifth node wants to declare data risks for the first field, the fifth node can send a data risk declaration request for the first field to the first node, so that the first node can obtain this information and perform other processing based on the request, such as sending the request to each node upstream of it or directly signing the request for approval.

[0084] It should be noted that in this application, for any field, the task corresponding to the field is used to generate, use or process the field, so that the task refers to the task that references the field, so that the task can express the process related to the field. It can be seen that in a possible implementation, for any field, the task corresponding to the field satisfies the following constraints: the identifier of the field, such as the name, exists in the script used to implement the task corresponding to the field.

[0085] It should also be noted that the present application does not limit the implementation method of the fifth node triggering the data risk reporting request. For example, when a data risk reporting page is displayed on the terminal corresponding to the fifth node, the manager of the fifth node can first fill in the identifier of the first field that needs to be reported for risk, the identifier of the data table to which the first field belongs, the risk type to which the first field belongs, the risk level reached by the first field, the usage scenario of the first field, the data quality requirements of the first field, the identifier of the manager of the first field (such as name or account number), and other information on the page, so that after the manager triggers the operation on the corresponding button on the page, a data risk reporting request is generated based on the content filled in on the page, so that the data risk reporting request carries at least these contents, and the data risk reporting request is sent to the first node.

[0086] It should also be noted that in the present application, for any node, the terminal corresponding to the node is used to provide services for the manager (Owner) of the node, so that the manager can complete some related matters such as updating, querying, etc. for the fields, data tables and tasks in the node through some interactive operations on the terminal.

[0087] Case 2: When the first node is any node other than the first node in the data link, such as a leaf node, if the first node wants to declare data risk for the first field, the first node can trigger a data risk declaration request for the first field.

[0088] It should be noted that the present application does not limit the implementation method of the first node triggering the data risk reporting request. For example, when a data risk reporting page is displayed on the terminal corresponding to the first node, the manager of the first node can first fill in the identifier of the first field that needs to be reported for risk, the identifier of the data table to which the first field belongs, the risk type to which the first field belongs, the risk level reached by the first field, the usage scenario of the first field, the data quality requirements of the first field, the identifier of the manager of the first field, and other information on the page, so that after the manager triggers the operation on the corresponding button on the page, a data risk reporting request is generated based on the content filled in on the page, so that the data risk reporting request carries at least these contents, and the data risk reporting request is sent to the first node.

[0089] Based on the relevant content of the data risk reporting request above, it can be known that the data risk reporting request for the first node can be triggered by the first node itself, or by the user of the task corresponding to the first field in the first node.

[0090] S102: Perform field-level lineage tracing processing based on the field identifier to obtain a processing result, which is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node, and the second node is located upstream of the first node.

[0091] Among them, the field-level lineage tracing process is used to find objects that have a lineage with the first field and are located upstream of the first field, such as fields, data tables, tasks and other objects.

[0092] In addition, the present application does not limit the implementation method of field-level lineage tracing processing. For example, it can adopt any existing or future method that can perform field-level lineage tracing processing based on the identifier of the first field, such as implementing it with the help of a machine learning model with field-level lineage tracing processing function.

[0093] The processing result refers to the result obtained by performing field-level lineage tracing processing according to the identifier of the first field, so that the processing result can represent objects that have a lineage with the first field and are located upstream of the first field, such as fields, data tables, tasks and other objects.

[0094] It can be seen that, in one possible implementation, the above processing result includes at least the second field in the second node, and the task corresponding to the second field in the second node, so that the processing result can indicate that there is a blood relationship between the first field and the second field, and there is a blood relationship between the first field and the task corresponding to the second field in the second node, such as there is a blood relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node, etc.

[0095] Among them, the second node refers to a node that exists in the data link to which the first node belongs, is located upstream of the first node, and has a certain blood relationship with the first node, and the second node satisfies at least the following constraints: the second node and the first node belong to the same data link, the second node is located upstream of the first node, and the second field in the second node has a blood relationship with the first field in the first node, such as a father-son relationship, a grandfather-grandson relationship, a great-grandfather-great-grandson relationship, etc.

[0096] It should be noted that the present application does not limit the implementation method of the blood relationship in the above paragraph. For example, if the second node is the first-level upstream of the first node, the first field in the first node can be obtained by processing the second field in the second node, so that the second field and the first field have a parent-child relationship, also known as a first-level blood relationship. For another example, if the second node is the second-level upstream of the first node, the first field in the first node is obtained by processing the corresponding field in the first-level upstream of the first node, and the corresponding field in the first-level upstream is obtained by processing the second field in the second node, so that the second field and the first field have a grandfather-grandson relationship, also known as a second-level blood relationship.

[0097] In addition, the present application does not limit the implementation method of the second node above. For example, the second node may include a level 1 upstream node (for example, node C) that has a blood relationship with the first field in the first node, a level 2 upstream node (for example, node B) that has a blood relationship with the first field in the first node, a level 3 upstream node (for example, node A) that has a blood relationship with the first field in the first node, and so on (and so on).

[0098] In addition, for the second field in the second node above, the second field refers to a field existing in the second node and having a blood relationship with the first field in the first node, so that the second field and the first field satisfy the following constraint: the first field is obtained by performing at least one level of processing on the second field.

[0099] In addition, for the second field in the second node above, the task corresponding to the second field may refer to a task existing in the second node and having a blood relationship with the first field in the first node, so that the task corresponding to the second field is used to generate, use or process the second field. It can be seen that in a possible implementation, the task corresponding to the second field may satisfy the following constraint: the identifier of the second field, such as a name, exists in the script used to implement the task corresponding to the second field.

[0100] In fact, in some scenarios, there are multiple tasks in the second node that have a blood relationship with the first field in the first node. Therefore, in order to better improve efficiency, the present application also provides a possible implementation method of the above processing results. In this method, when the tasks corresponding to the second field include multiple tasks, and the path length between the target task in the multiple tasks and the task corresponding to the first field is not greater than the path length between any other task in the multiple tasks except the target task and the task corresponding to the first field, the processing result is specifically used to indicate: there is a blood relationship between the task corresponding to the first field in the first node and the target task, so that risk-related processing is only performed on the target task in the future, such as risk labeling processing and risk warning processing. Among them, the target task refers to the task that exists in the second node and has the closest blood relationship with the first field in the first node. The path length is used to describe the level of blood relationship, so that the path length can describe the distance between the two parties with blood relationship.

[0101] It can be seen that in one possible implementation, when there are multiple tasks in the second node that have a blood relationship with the first field in the first node, the above S102 can specifically be: perform field-level blood relationship tracing processing according to the identifier of the first field, so that when tracing back to the task that exists in the second node and has the closest blood relationship with the first field, generate a processing result based on the "task that has the closest blood relationship with the first field", and directly execute the tracing processing for the upstream node of the second node or end the tracing processing, so that it can be achieved after finding the "task that has the closest blood relationship with the first field". No traceability processing will be performed on other tasks in the second node, so that subsequent risk processing only needs to be performed on the "task that has the closest blood relationship with the first field", such as risk labeling processing and risk prompting processing. This can effectively avoid defects caused by repeated labeling or prompting of the same risk when there are multiple tasks in the second node that have a blood relationship with the first field in the first node, such as low efficiency, high redundancy, and interference with subsequent impact assessment. This is conducive to improving efficiency and impact assessment effects, such as improving assessment efficiency and reducing the information redundancy of assessment results.

[0102] Based on the relevant content of S102 above, it can be known that after obtaining the data risk declaration request triggered for the first field in the first node, field-level lineage tracing processing is performed based on the field identifier carried by the request, that is, the identifier of the first field, to obtain a processing result, so that the processing result includes objects with a first-level lineage relationship with the first field (such as a parent node, the corresponding field in the parent node, and the corresponding task, etc.), objects with a second-level lineage relationship with the first field (such as a grandparent node, the corresponding field in the grandparent node, and the corresponding task, etc.), objects with a third-level lineage relationship with the first field (such as a great-grandfather node, the corresponding field in the great-grandfather node, and the corresponding task, etc.),... (and so on), so that the processing result can more comprehensively and accurately represent the objects that exist in the data link and have a lineage relationship with the first field, so that corresponding processing can be performed based on the object in the future, such as risk labeling processing and risk warning processing.

[0103] S103: Mark the task corresponding to the second field with the first information, and send the second information to the terminal corresponding to the second node, where the terminal corresponding to the second node is used to display the second information, the first information includes the risk type, and the second information is determined based on part or all of the information carried by the data risk reporting request.

[0104] The first information refers to the information required to be used when marking a task that is related to the first field and located upstream, such as the risk type of the first field, so that the first information can indicate what kind of risk may be presented in the first node (or the first field) when an error occurs in the task. It can be seen that in a possible implementation, the first information can include the risk type of the first field.

[0105] In addition, the present application does not limit the labeling method of the first information above. For example, it can be implemented with the help of a pre-built method or device that can perform information labeling processing for a task.

[0106] The terminal corresponding to the second node is used to provide services to the manager of the second node, such as services for performing related processing on objects in the second node, such as fields, data, tasks, etc., so that the manager can better manage the objects in the second node with the help of the terminal.

[0107] The second information is used to indicate that the second field in the second node, the data table to which the second field belongs, the task corresponding to the second field, and other objects will affect the first node or the first field in the first node, so that the second information can represent the risks that may occur in the first node when an error occurs in the object.

[0108] In addition, the second information is determined based on part or all of the information carried in the above data risk reporting request, such as the risk type of the first field, the risk level of the first field, the usage scenario of the first field, the identifier of the first field, the data table to which the first field belongs, the data quality requirements of the first field, the identifier of the manager of the first field, etc., so that the second information can better represent the impact on the first node when the second node fails.

[0109] In addition, in order to better improve the prompt effect, the present application provides a possible implementation method of the second information. In this method, the determination process of the second information is not only based on part or all of the information carried by the above data risk reporting request, but also based on at least one item of information in the second field in the second node, so that the second information can not only indicate the impact on the first node when the second node fails, but also indicate which objects in the second node will cause risks to the first node when errors occur.

[0110] In addition, for at least one item of information in the second field of the second node above, the at least one information can describe the characteristics of the second field, such as who manages it, the field name, which data table it belongs to, etc., so that the at least one item of information can include at least the identifier of the manager of the second node, the identifier of the second field, and at least one of the identifiers of the data table to which the second field belongs.

[0111] In fact, in order to better improve the impact assessment effect, the present application also provides a possible implementation method of S103 above. In this method, when the task corresponding to the second field includes multiple tasks, and the path length between the target task in the multiple tasks and the task corresponding to the first field is not greater than the path length between any other task in the multiple tasks except the target task and the task corresponding to the first field, the S103 can specifically be: marking the first information for the target task, and sending the second information to the terminal corresponding to the second node, so that the terminal corresponding to the second node is used to display the second information. This can effectively avoid the defects caused when the risk type is marked or prompted for each task in the multiple tasks, thereby helping to improve the impact assessment effect, such as improving the assessment efficiency and reducing the information redundancy of the assessment results.

[0112] In addition, in order to better improve the impact assessment effect, the present application also provides a possible implementation method of S103 above. In this method, the S103 can specifically be: marking the first information for the task corresponding to the second field, sending the second information to the terminal corresponding to the second node, and marking the third information for the second field in the data table of the second node, where the third information includes the risk type.

[0113] It can be seen that, under a possible implementation mode, after tracing back to the second node according to the identifier of the first field in the first node, the following operations ①-③ can be performed: ① Marking the tasks existing in the second node that have a blood relationship with the first field, such as the tasks with the closest blood relationship (also known as checkpoints), so that the marked tasks at least include the label content of the risk type of the first field, so that the label content can indicate the risks that may be caused when an error occurs in the task; ② Marking the fields existing in the second node that have a blood relationship with the first field, so that the marked fields at least include the label content of the risk type of the first field, so that the label content can indicate the risks that may be caused when an error occurs in the field; ③ Sending the second information to the terminal corresponding to the second node for display, so that the manager of the second node can promptly learn from the second information the impact of the second node on the first node, which is conducive to enriching the risk perception method of the upstream node, thereby more effectively avoiding failures caused by the upstream node's lack of perception of the risks of the downstream node.

[0114] It should be noted that the present application does not limit the relationship between the execution times of the three operations ① to ③ in the above paragraph, for example, the three operations are the same. For another example, the three operations can be executed in a certain order.

[0115] Based on the relevant contents of S101 to S103 above, it can be known that for any data link, when the data link includes a first node and some nodes located upstream of the first node, such as a second node, if a data risk reporting request triggered for a first field in the first node is detected, field-level lineage tracing processing is first performed based on the field identifier carried by the data risk reporting request to obtain a processing result, so that the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node; then the first information is marked on the task corresponding to the second field, and the second information is sent to the terminal corresponding to the second node, so that the terminal corresponding to the second node is used to display the second information.

[0116] Among them, because the first information includes the risk type carried by the data risk reporting request, after the first information is marked for the task corresponding to the second field, the second node or the manager of the second node can learn from the marked content of the task that when an error occurs in the task or the task is changed, it may cause risks to the first node, thereby determining that when an error occurs in the task or the task is changed, it may have an impact on the first node, such as a high-risk impact. In this way, it is possible to quickly determine the impact of the task when changes are made or failures occur with the help of the marked content, which is beneficial to improving the efficiency of impact determination, and further beneficial to improving the data link management effect.

[0117] In addition, because the second information is determined based on part or all of the information carried by the data risk reporting request, the second information can better indicate that when some objects in the second node, such as tasks, fields, data tables, etc., have errors or changes, they can affect the first node, so that the second information can more accurately indicate the impact of the second node on the first node, such as high-risk impact, and thus enable the manager of the second node to learn from the second information the impact of the second node on the first node, so that when the object fails or changes subsequently, the impact of the object can be quickly determined from the second information, which is beneficial to improving the efficiency of impact determination and thus beneficial to improving the data link management effect.

[0118] Based on the above three paragraphs, it can be seen that for any data link, the downstream node in the data link can inform its upstream node of its risky fields through declaration, so that the upstream node can accurately and timely know that when some fields, tasks or data tables in the upstream node are changed (or errors occur), it will cause risks to the downstream node. This is conducive to achieving efficient, accurate, and comprehensive impact assessment, thereby reducing failures, such as reducing failures caused by the upstream node's inability to perceive the risks involved in the downstream node to 0, which is conducive to improving the data link management effect.

[0119] It should be noted that the present application does not limit the execution subject of the above S101 to S103. For example, the S101 to S103 may be executed by the terminal corresponding to the first node or a pre-built information platform, so that the S101 to S103 can describe how to implement the risk declaration processing process of the downstream node. The information platform can communicate with the terminals corresponding to each node in the data link.

[0120] In fact, in order to better improve the impact assessment effect, the present application also provides a data link management method for implementing impact determination processing, such as Figure 2As shown, the data link management method includes the following S201-S203. Figure 2 A flowchart of a data link management method provided in an embodiment of the present application.

[0121] S201: Receive an impact determination request triggered for a target object in a second node, the impact determination request is used to request determination of nodes affected by the target object, the object identifier carried in the impact determination request is used to identify the target object, and the target object includes at least one field in the second node; the risk declaration processing process of at least one first node located downstream of the second node has been executed, and the risk declaration processing process is implemented using any implementation method of the above data link management method.

[0122] Among them, the second node refers to the node that needs to be impact assessed, such as the node A above; and the target object in the second node refers to the object that exists in the second node and needs to be impact assessed, such as a field, a data table, or a task, so that the target object can include at least one field in the second node. It should be noted that this application does not limit the implementation method of the target object. For example, the target object can be implemented using a field, a data table, or a task in the second node.

[0123] In addition, the present application does not limit the implementation method of the second node above. For ease of understanding, two examples are used for explanation below.

[0124] Example 1, in some scenarios, such as change scenarios, the second node may satisfy the following constraints: the second node is used to perform change processing on the target object, so an impact assessment process needs to be performed on the target object to determine which nodes may be affected when the target object is changed.

[0125] Example 2. In some scenarios, such as fault analysis scenarios, the second node can satisfy the following constraints: the target object in the second node is obtained by locating the fault occurring in the third node, and the second node is located upstream of the third node, so that the target object can represent the object that exists upstream of the third node and causes the fault. Therefore, it is necessary to perform an impact assessment on the target object to determine which nodes the target object may affect in addition to the impact on the third node. This is conducive to timely discovery of other nodes where risks have occurred, which is conducive to improving safety.

[0126] The third node refers to a node in the data link that is located downstream of the second node and has a fault. It can be seen that in a possible implementation, the third node satisfies the following constraints: the third node and the second node belong to the same data link, and there is a blood relationship between a field in the third node and the target object in the second node.

[0127] The impact determination request is used to request to determine whether there is a node in the data link that is affected by the target object in the second node; and the object identifier carried in the impact determination request is used to identify the target object.

[0128] In addition, the present application does not limit the triggering time of the above impact determination request. For example, before the impact determination request is triggered, the risk declaration processing process of at least one first node located downstream of the second node has been completed, and the risk declaration processing process of each first node is implemented by any implementation method of the above data link management method, such as the method shown in S101-S103 above. Among them, the first node refers to the risk declaration node located downstream of the second node and has completed the risk declaration processing process, such as the above node D.

[0129] In addition, the present application does not limit the implementation method of S201 above. For example, if the S201 is implemented by the terminal corresponding to the second node, then when a declaration information list and a query box are displayed on the terminal, the declaration information list includes risk declaration information corresponding to the at least one first node, and the query box is used to receive query keywords output for the declaration information list, the S201 can specifically be: receiving an identifier of a target object input into the query box, such as the name of a data table or the name of a field, etc., so that the risk declaration information matching the identifier can be subsequently found from the declaration information list.

[0130] Among them, the declaration information list refers to the relevant information of the risks declared by the risk declaration node that has completed the risk declaration processing process and is displayed on the terminal corresponding to the second node, such as which field in which data table in the second node is affected, the identifier of the declarant, the identifier of the manager of the second node, and other information.

[0131] It can be seen that the declaration information list may include risk declaration information corresponding to at least one of the first nodes above. For any first node, the risk declaration information corresponding to the first node is used to describe the characteristics of the risk in the first node, such as which field in which data table in the second node is affected, the identifier of the declarant, the identifier of the manager of the second node, etc.; and this application does not limit the implementation method of the risk declaration information, for example, the implementation method of the risk declaration information is similar to the implementation method of the second information above.

[0132] S202: Perform query processing according to at least one first node and an object identifier to obtain a query result, where the query result is used to indicate that one or more first nodes are affected by the target object.

[0133] The query processing refers to the result of searching for information matching the identifier of the target object within the range defined by at least one first node, so that the query result can indicate which nodes among the first nodes are affected by the target object.

[0134] It can be seen that in one possible implementation, when the target object includes at least one field, the query result can be used to indicate the existence of a blood relationship between the fields in one or more first nodes and part or all of the at least one field, so that the query result can indicate which first nodes are affected by the target object.

[0135] Based on the above two paragraphs, it can be seen that when conducting an impact assessment on a target object, the query processing is not performed on the entire data link, but on the scope defined by all risk reporting nodes. This is conducive to improving query efficiency and thus improving impact assessment efficiency.

[0136] In addition, the present application does not limit the implementation method of S202 above. For example, if the target object is a task, then S202 may specifically be: based on the annotation information of the task, quickly determine the first node that has a field-level blood relationship with the task as a query result. For another example, if the target object is a field, then S202 may specifically be: based on the annotation information of the field or the annotation information of the task corresponding to the field, quickly determine the first node that has a field-level blood relationship with the field as a query result. For another example, if the target object is a data table, then S202 may specifically be: based on the annotation information of each field in the data table or the annotation information of the task corresponding to each field, quickly determine the first node that has a field-level blood relationship with the data table as a query result.

[0137] In addition, in order to better improve efficiency, the present application also provides a possible implementation method of S202 above. In this method, when S202 is implemented by the terminal corresponding to the second node and a declaration information list is displayed on the terminal, S202 can specifically be: according to the above object identifier, the declaration information list is queried and processed to obtain a query result, and the query result is used to indicate the risk declaration information that matches the object identifier, so that the query result can represent the relevant information of the risks declared by the nodes in the declaration information list that have a field-level blood relationship with the target object.

[0138] S203: Feedback is provided to the impact determination request based on the query result.

[0139] It should be noted that the present application does not limit the implementation method of S203. For example, it may specifically be: the terminal corresponding to the second node displays the query result in a certain manner.

[0140] It can be seen that, in a possible implementation, when S203 is implemented by the terminal corresponding to the second node, and a declaration information list is being displayed on the terminal, S203 can specifically be: based on the query result, update the display content on the terminal, and the updated display content is used to indicate the risk declaration information that matches the above object identifier, so that the updated display content can indicate the relevant information of the risk declared by the node that exists in the declaration information list and has a field-level blood relationship with the target object. It should be noted that the present application does not limit the implementation method of the "updated display content". For example, the updated display content may include risk declaration information that matches the object identifier, but does not include other information in the declaration information list except the "risk declaration information that matches the object identifier".

[0141] Based on the relevant contents of S201 to S203 above, it can be known that for any data link, after the downstream node in the data link informs its upstream node of its risky fields through declaration, the upstream node can use this information to determine that when some fields, tasks or data tables in the upstream node are changed (or errors occur), it will have an impact on the downstream node. This is conducive to achieving efficient, accurate, and comprehensive impact assessment, thereby reducing failures, such as reducing failures caused by the upstream node's inability to perceive the risks involved in the downstream node to zero, which is conducive to improving the data link management effect.

[0142] It should be noted that the present application does not limit the execution entity of S201 to S203 above. For example, S201 to S203 can be executed by the terminal corresponding to the second node or a pre-built information platform, so that S201 to S203 can describe how to implement the impact assessment process of the upstream node.

[0143] In addition, in order to better improve security, the present application also provides a possible implementation of the data link management method, in which, when at least one of the first nodes above includes a target node, and the query result above is used to indicate that the target node is affected by the target object, the data link management method may at least include the following step 21. The execution time of step 21 is later than the execution time of S202 above.

[0144] Step 21: Send first prompt information to the target node, where the first prompt information is used to indicate that the target node is affected by the target object in the second node.

[0145] Among them, the target node refers to a node that exists in at least one of the first nodes above and has a field-level blood relationship with the target object in the second node, such as node D above, so that the target node can represent a risk declaration node that has completed the risk declaration processing process and has a field-level blood relationship with the target object.

[0146] The first prompt information is used to indicate that the target node is affected by the target object in the second node, so that the manager of the target node can, after obtaining the information, focus on whether there are risks posed by the fields in the target node that have a blood relationship with the target object, which is conducive to improving security.

[0147] Based on the relevant content of step 21 above, it can be known that in some scenarios, for the target object in the second node, after determining the risk reporting nodes that have a field-level blood relationship with the target object, it is necessary not only to generate an impact assessment report for the target object based on these risk reporting nodes, so that the impact assessment report can indicate that the target object will affect these risk reporting nodes, but also to send corresponding prompt information to these risk reporting nodes, so that the managers of these risk reporting nodes can pay more attention to the occurrence of risks based on the prompt information, thereby effectively avoiding failures caused by downstream changes to upstream or unaware of errors, which is conducive to improving security and thus improving data link management effects.

[0148] In addition, in order to better improve security, the present application also provides a possible implementation of the data link management method, in which, when the second node is used to perform a change process on the target object, the data link management method may at least include the following step 31. The present application does not limit the execution time of step 31.

[0149] Step 31: Send a second prompt message to the fourth node, where the second prompt message is used to instruct the target object in the second node to perform a change process, and the fourth node is located downstream of the second node, and the fourth node is adjacent to the second node.

[0150] The fourth node refers to a node existing in the data link and located one level downstream of the second node, such as node B. It can be seen that, in a possible implementation, the fourth node at least satisfies the following constraints: the fourth node and the second node belong to the same data link, the fourth node is located downstream of the second node, and the position of the fourth node on the data link is adjacent to the position of the second node on the data link.

[0151] The second prompt information is used to indicate that the target object in the second node is to be changed, so that the manager of the fourth node can learn from the prompt information that the target object is changed, thereby enabling the manager of the fourth node to focus on objects in the fourth node that have a blood relationship with the target object, such as fields, data tables, and tasks, to see if errors occur in the near future, which is conducive to improving security.

[0152] Based on the relevant content of step 31 above, it can be known that in some scenarios, for a data link, if it is detected that a target object in a node of the data link, such as node A, is changed, a prompt message can be sent to the first-level downstream node of the node, so that the first-level downstream node can be informed of the change of the target object from the prompt information, so that the manager of the first-level downstream node can focus on the objects in the first-level downstream node that have a blood relationship with the target object, such as fields, data tables, and tasks, to see if there are any errors in the near future. This is conducive to improving security and thus improving the data link management effect.

[0153] Based on the relevant content of the data link management method provided by the present application, it can be known that the present application provides a full-link perception solution, which includes: for a data link, the downstream party can register the data quality requirements, usage scenarios, risk types, risk levels and other information of high-risk fields on the information platform for unified management, so that the information platform can pass the relevant information of high-risk fields to the upstream party through field-level blood relationships, and perform risk tagging processing on some objects in the upstream party, such as fields, data tables or tasks. In this way, the upstream party can promptly obtain the relevant information of the high-risk fields in the downstream party through notification messages and marking content, so that when the upstream party makes changes or errors occur, it can efficiently, accurately and comprehensively conduct impact assessments to reduce accidents, which is conducive to improving the data link management effect.

[0154] In addition, for the full-link perception solution mentioned above, the solution also includes: (1) Change control based on the records that have been successfully reported and the content that has been marked to ensure that the change control can achieve controllable, accurate notification, and strong protection of the R&D process; (2) Hierarchical monitoring configuration and governance for risk reporting nodes, nodes in the data link, and checkpoints (such as tasks with the closest blood relationship); (3) For data links that have completed some risk reporting processing, the upstream party can query and process from the downstream risk reporting node to quickly conduct high-risk impact assessment, which is conducive to improving the efficiency of impact assessment. In this way, the solution can reduce the failure caused by unawareness of risks to zero.

[0155] In addition, for the full-link perception solution mentioned above, this full-link perception solution is to open up the core link from the data user end to the data production end from the bottom up by tracing the field-level lineage, and through the risk reporting and automatic transparent transmission capabilities, timely and accurate notification of risks and information, and prompt risk issues in the data link, collaborate with upstream parties to improve data quality assurance, and promptly inform upstream and downstream or data quality inspection parties when data changes occur, to avoid accidents such as asset losses and customer complaints.

[0156] In addition, for the full-link perception solution mentioned above, the goals of this solution are: perception, transparent transmission, and protection. The use scenarios of this solution include high-security scenarios such as asset loss, customer complaints, core reports, and management decisions. The risk declarants in this solution include managers of leaf nodes in the data link (such as the R&D party of the data lake or data warehouse) and users of the data in the leaf node. The risk declaration content in this solution includes risk type, risk level, fault level, usage scenario, business party, data quality requirements, etc. The risk dependency solution in this solution includes managers of upstream lineage tasks. The signing action in this solution is: lightweight strategy, that is, the signing is completed when the declaration is successful or the transparent transmission is successful, so that the information platform will notify the manager of the upstream card point and mark it on the second day of the declaration, so that the notification information and marking information can include usage scenarios, risk types, risk levels, requirements (such as data quality requirements, protection requirements, etc.), related people and other information. The data in this solution can include offline data and / or online data.

[0157] Furthermore, for the declaration signing management in the full-link perception solution mentioned above, it can be specifically: based on field-level lineage identification, the full-link needs to sign the guarantee task, trace the source within and across projects, and notify the task manager or data quality inspector to sign the approval, such as the approval signing information shown in Table 1 below, and pass through the specific use risk scenarios and the required guarantee strength, so as to provide quality signing process management for core link nodes. In addition, when a declaration task is in the process of signing and approval, the initiator of the declaration task can cancel the declaration task to invalidate the information that has been signed for the declaration task in the data link. In addition, if the business scenario of a declared task changes, such as non-existence or update, so that the task no longer involves high risk, the initiator of the task can revoke the signed information to invalidate the information that has been signed for the task in the data link, thereby effectively avoiding the interference caused by the information in the impact assessment process, such as interference in efficiency and interference in accuracy.

[0158] Secondly, in the full-link perception solution mentioned above, after obtaining the signature information and the field-level lineage relationship corresponding to the signature information, queries can be made based on these contents to support subsequent quality governance and assurance work, such as lineage links and quality protocols, so that the following matters can be further promoted in the future: ① Change control based on high-security lineage tags, so that the upstream link of high-risk fields needs to strengthen the control process; ② Full-link quality assurance level: Based on the full-link quality assurance specification, identify the assurance level, such as quality monitoring coverage, so as to promote governance in a targeted manner (such as basic constraints such as table non-empty, table fluctuation, primary key unique, primary key non-empty, similar to at least one field-level constraint coverage 100%, asset loss field valid value range, sum (asset loss field) valid value, sum (asset loss field) daily / weekly volatility, task level constraints, etc.); ③ Change impact broadcast: After the upstream link code is changed, the link change broadcast can be carried out based on the above lineage link and quality protocol, and regression testing can be carried out. ④ Impact assessment: In the data emergency process, accurate impact assessment and emergency notification can be carried out.

[0159]

[0160] Table 1 Approval Signature Details

[0161] Based on the data link management method provided in the embodiment of the present application, the embodiment of the present application also provides a data link management device. Figure 3 Explain and illustrate. Figure 3 This is a schematic diagram of the structure of a data link management device provided in an embodiment of the present application. It should be noted that for the technical details of the data link management device provided in an embodiment of the present application, please refer to the relevant content of the data link management method above.

[0162] like Figure 3 As shown, the data link management device 300 provided in the embodiment of the present application includes:

[0163] A first receiving unit 301 is used to receive a data risk reporting request triggered for a first field in a first node, where the data risk reporting request is used to indicate a risk type and a risk level of the first field, and a field identifier carried by the data risk reporting request is used to identify the first field;

[0164] A first processing unit 302 is used to perform field-level lineage tracing processing according to the field identifier to obtain a processing result, wherein the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node, and the second node is located upstream of the first node;

[0165] The first feedback unit 303 is used to mark the first information on the task corresponding to the second field, and send second information to the terminal corresponding to the second node, the terminal corresponding to the second node is used to display the second information, the first information includes the risk type, and the second information is determined based on part or all of the information carried by the data risk reporting request.

[0166] In a possible implementation manner, the task corresponding to the second field includes multiple tasks;

[0167] The path length between a target task among the multiple tasks and a task corresponding to the first field is not greater than the path length between any other task among the multiple tasks except the target task and the task corresponding to the first field;

[0168] The processing result is specifically used to indicate that: there is a blood relationship between the task corresponding to the first field in the first node and the target task;

[0169] The first feedback unit 303 is specifically configured to: label the target task with first information.

[0170] In a possible implementation manner, the first feedback unit 303 is further configured to: mark the second field in the data table of the second node with third information, where the third information includes the risk type.

[0171] In one possible implementation, the second information is also determined based on at least one item of information of the second node; the at least one item of information includes at least one of an identifier of the manager of the second node, an identifier of the second field, and an identifier of a data table to which the second field belongs.

[0172] In a possible implementation manner, the data link management device 300 is deployed at a terminal corresponding to the first node.

[0173] Based on the relevant content of the above-mentioned data link management device 300, it can be known that the working principle of the data link management device 300 provided in the present application includes: for any data link, when the data link includes a first node and some nodes located upstream of the first node, such as a second node, if a data risk reporting request triggered for a first field in the first node is detected, field-level lineage tracing processing is first performed based on the field identifier carried by the data risk reporting request to obtain a processing result, so that the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node; then the first information is marked on the task corresponding to the second field, and the second information is sent to the terminal corresponding to the second node, so that the terminal corresponding to the second node is used to display the second information. Among them, because the first information includes the risk type carried by the data risk reporting request, after the first information is marked for the task corresponding to the second field, the second node or the manager of the second node can learn from the marked content of the task that when an error occurs in the task or the task is changed, it may cause risks to the first node, thereby determining that when an error occurs in the task or the task is changed, it may have an impact on the first node, such as a high-risk impact. In this way, it is possible to quickly determine the impact of the task when changes are made or failures occur with the help of the marked content, which is conducive to improving the efficiency of impact determination. In addition, because the second information is determined based on part or all of the information carried by the data risk reporting request, the second information can better indicate that when some objects in the second node, such as tasks, fields, data tables, etc., have errors or changes, they can affect the first node, so that the second information can more accurately indicate the impact of the second node on the first node, such as high-risk impact, and then the manager of the second node can learn from the second information the impact of the second node on the first node, so that when the object fails or changes subsequently, the impact of the object can be quickly determined from the second information, which is conducive to improving the efficiency of impact determination.

[0174] Based on the data link management method provided in the embodiment of the present application, the embodiment of the present application also provides a data link management device. Figure 4 Explain and illustrate. Figure 4 This is a schematic diagram of the structure of a data link management device provided in an embodiment of the present application. It should be noted that for the technical details of the data link management device provided in an embodiment of the present application, please refer to the relevant content of the data link management method above.

[0175] like Figure 4 As shown, the data link management device 400 provided in the embodiment of the present application includes:

[0176] A second receiving unit 401 is used to receive an impact determination request triggered for a target object in a second node, the impact determination request is used to request determination of a node affected by the target object, the object identifier carried by the impact determination request is used to identify the target object, and the target object includes at least one field in the second node; a risk declaration processing process of at least one first node located downstream of the second node has been executed, and the risk declaration processing process is implemented by using any implementation of the data link management method provided by the present application;

[0177] A second processing unit 402 is configured to perform query processing according to the at least one first node and the object identifier to obtain a query result, wherein the query result is used to indicate that one or more first nodes are affected by the target object;

[0178] The second feedback unit 403 is configured to provide feedback on the impact determination request according to the query result.

[0179] In a possible implementation manner, the data link management device 400 is deployed in a terminal corresponding to the second node.

[0180] The data link management device 400 further includes:

[0181] An information display unit, configured to display a declaration information list and a query box on the terminal, wherein the declaration information list includes risk declaration information corresponding to the at least one first node;

[0182] The second receiving unit 401 is specifically configured to: receive the identifier of the target object input into the query box;

[0183] The second processing unit 402 is specifically used to: perform query processing on the declaration information list according to the object identifier to obtain a query result, wherein the query result is used to indicate the risk declaration information matching the object identifier;

[0184] The second feedback unit 403 is specifically used to update the display content on the terminal according to the query result, and the updated display content is used to indicate the risk declaration information matching the object identifier.

[0185] In one possible implementation manner, the at least one first node includes a target node;

[0186] The query result is used to indicate that the target node is affected by the target object;

[0187] The second feedback unit 403 is further used to: send first prompt information to the target node, where the first prompt information is used to indicate that the target node is affected by the target object in the second node.

[0188] In a possible implementation manner, the second node is used to perform change processing on the target object;

[0189] or,

[0190] The target object in the second node is obtained by locating a fault occurring in the third node, and the second node is located upstream of the third node.

[0191] In a possible implementation manner, the second node is used to perform change processing on the target object;

[0192] The data link management device 400 further includes:

[0193] An information sending unit is used to send second prompt information to a fourth node, wherein the second prompt information is used to indicate that a target object in the second node is to be changed, and the fourth node is located downstream of the second node, and the fourth node is adjacent to the second node.

[0194] Based on the relevant content of the above-mentioned data link management device 400, it can be known that the working principle of the data link management device 400 provided in the present application is: for any data link, after the downstream node in the data link informs its upstream node of its risky fields through declaration, the upstream node can use this information to determine that when some fields, tasks or data tables in the upstream node are changed (or errors occur), it will have an impact on the downstream node. This is conducive to achieving efficient, accurate, and comprehensive impact assessment, thereby reducing failures, such as reducing failures caused by the upstream node's inability to perceive the risks involved in the downstream node to zero.

[0195] In addition, an embodiment of the present application also provides an electronic device, which includes a processor and a memory: the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs in the memory, so that the electronic device executes any implementation of the data link management method provided in the embodiment of the present application.

[0196] See also Figure 5, which shows a schematic diagram of the structure of an electronic device 500 suitable for implementing the embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0197] like Figure 5 As shown, the electronic device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0198] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 The electronic device 500 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0199] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0200] The electronic device provided by the embodiment of the present disclosure and the method provided by the above embodiment belong to the same inventive concept, and the technical details not fully described in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0201] An embodiment of the present application also provides a computer-readable medium, in which instructions or computer programs are stored. When the instructions or computer programs are executed on a device, the device executes any implementation of the data link management method provided in the embodiment of the present application.

[0202] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0203] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (Hyper Text Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0204] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0205] The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device can execute the method.

[0206] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0207] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0208] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a unit / module does not, in some cases, constitute a limitation on the unit itself.

[0209] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0210] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0211] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0212] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0213] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0214] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0215] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be 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 the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A data link management method, characterized in that: The method comprises: receiving a data risk reporting request triggered for a first field in a first node, the data risk reporting request being used to indicate a risk type and a risk level of the first field, and a field identifier carried by the data risk reporting request being used to identify the first field; Perform field-level lineage tracing processing according to the field identifier to obtain a processing result, wherein the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node, and the second node is located upstream of the first node; The first information is marked on the task corresponding to the second field, and the second information is sent to the terminal corresponding to the second node. The terminal corresponding to the second node is used to display the second information. The first information includes the risk type. The second information is determined based on part or all of the information carried by the data risk reporting request.

2. The method according to claim 1, characterized in that The task corresponding to the second field includes multiple tasks; The path length between a target task among the multiple tasks and a task corresponding to the first field is not greater than the path length between any other task among the multiple tasks except the target task and the task corresponding to the first field; The processing result is specifically used to indicate that: there is a blood relationship between the task corresponding to the first field in the first node and the target task; The marking of the first information on the task corresponding to the second field includes: The target task is labeled with first information.

3. The method according to claim 1, characterized in that After obtaining the processing result, the method further includes: The second field in the data table of the second node is marked with third information, where the third information includes the risk type.

4. The method according to any one of claims 1 to 3, characterized in that: The second information is also determined based on at least one item of information of the second node; The at least one item of information includes at least one of an identifier of a manager of the second node, an identifier of the second field, and an identifier of a data table to which the second field belongs.

5. A data link management method, characterized in that: The method comprises: Receiving an impact determination request triggered for a target object in a second node, the impact determination request being used to request determination of nodes affected by the target object, the object identifier carried in the impact determination request being used to identify the target object, the target object including at least one field in the second node; a risk declaration processing procedure of at least one first node located downstream of the second node has been executed, the risk declaration processing procedure being implemented by using the data link management method according to any one of claims 1 to 4; Performing query processing according to the at least one first node and the object identifier to obtain a query result, wherein the query result is used to indicate that one or more first nodes are affected by the target object; Feedback is provided to the impact determination request based on the query result.

6. The method according to claim 5, characterized in that The method is applied to the terminal corresponding to the second node, Before receiving the impact determination request triggered on the target object in the second node, the method further includes: Displaying a declaration information list and a query box on the terminal, the declaration information list including risk declaration information corresponding to the at least one first node; The receiving an impact determination request triggered on a target object in a second node includes: receiving an identifier of the target object input into the query box; The query processing is performed according to the at least one first node and the object identifier to obtain a query result, including: According to the object identifier, query the declaration information list to obtain a query result, wherein the query result is used to indicate the risk declaration information matching the object identifier; The providing feedback on the impact determination request according to the query result includes: Based on the query result, the display content on the terminal is updated, and the updated display content is used to indicate the risk declaration information matching the object identifier.

7. The method according to claim 5, characterized in that The at least one first node comprises a target node; The query result is used to indicate that the target node is affected by the target object; After obtaining the query result, the method further includes: First prompt information is sent to the target node, where the first prompt information is used to indicate that the target node is affected by the target object in the second node.

8. The method according to any one of claims 5 to 7, characterized in that: The second node is used to perform change processing on the target object; or, The target object in the second node is obtained by locating a fault occurring in the third node, and the second node is located upstream of the third node.

9. The method according to claim 5, characterized in that The second node is used to perform change processing on the target object; The method further comprises: A second prompt message is sent to a fourth node, where the second prompt message is used to instruct a target object in the second node to undergo a change process, the fourth node being located downstream of the second node, and the fourth node is adjacent to the second node.

10. A data link management device, characterized in that: include: A first receiving unit, configured to receive a data risk reporting request triggered for a first field in a first node, wherein the data risk reporting request is used to indicate a risk type and a risk level of the first field, and a field identifier carried by the data risk reporting request is used to identify the first field; a first processing unit, configured to perform field-level lineage tracing processing according to the field identifier to obtain a processing result, wherein the processing result is used to indicate that there is a lineage relationship between the first field and the second field in the second node, and there is a lineage relationship between the task corresponding to the first field in the first node and the task corresponding to the second field in the second node, and the second node is located upstream of the first node; A first feedback unit is used to mark first information on the task corresponding to the second field, and to send second information to a terminal corresponding to the second node, wherein the terminal corresponding to the second node is used to display the second information, wherein the first information includes the risk type, and the second information is determined based on part or all of the information carried by the data risk reporting request.

11. A data link management device, characterized in that: include: A second receiving unit is configured to receive an impact determination request triggered for a target object in a second node, wherein the impact determination request is used to request determination of nodes affected by the target object, and the object identifier carried in the impact determination request is used to identify the target object, and the target object includes at least one field in the second node; A risk declaration process of at least one first node located downstream of the second node has been completed, wherein the risk declaration process is implemented by using the data link management method according to any one of claims 1 to 4; A second processing unit, configured to perform query processing according to the at least one first node and the object identifier to obtain a query result, wherein the query result is used to indicate that one or more first nodes are affected by the target object; The second feedback unit is used to provide feedback on the impact determination request according to the query result.

12. An electronic device, characterized in that: The device comprises: a processor and a memory; The memory is used to store instructions or computer programs; The processor is used to execute the instructions or computer programs in the memory so that the electronic device executes the method according to any one of claims 1 to 9.

13. A computer readable medium, characterized in that The computer-readable medium stores instructions or computer programs, and when the instructions or computer programs are executed on a device, the device executes the method according to any one of claims 1 to 9.

14. A computer program product, characterized in that It comprises a computer program carried on a non-transitory computer-readable medium, the computer program comprising a program code for executing the method according to any one of claims 1 to 9.

Images