Index link detail analysis method and device based on data consanguinity

Abstract

The invention discloses an index link detail analysis method and device based on data consanguinity. The method is characterized by comprising the following steps: receiving a link traceability query task, and identifying a target index and an index query condition corresponding to the link traceability query task; performing link query in an index processing logic link based on the target index and the index query condition, and determining a target processing logic link of the target index; performing iterative blood relationship tracing in a data blood relationship graph based on the target processing logic link and the index query condition, and determining data blood relationship detail information of the target index; and constructing a data consanguinity link detail map corresponding to the link traceability query task based on the data consanguinity detail information and the target processing logic link. In the index link analysis process, the detail condition of the most source of the selected data can be directly checked, the interpretability of the index is greatly improved, and the analysis efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of index analysis, and in particular to an index link detail analysis method and device based on data blood relationship. BACKGROUND

[0002] Under the background of digital management, enterprises build a multi-level index system covering core fields such as finance, sales and operation to accurately understand the overall business situation. In the multi-level index system, there are usually different types of indexes, i.e. atomic indexes, derivative indexes and composite indexes. Atomic indexes, as the cornerstone of data, record the most basic business information. Derivative indexes and composite indexes process basic data through specific rules, such as "gross profit index = revenue index - cost index" and "cost index = structural cost index + non-structural cost index". Such clear mathematical operation relationships constitute the processing logic of indexes. Based on this logical framework, the existing BI (Business Intelligence) tools and intelligent question-answering systems can perform index link penetration analysis when analyzing composite indexes / derivative indexes. Although the existing technology index penetration or fluctuation attribution analysis displays the values and fluctuations of all indexes in the processing link, the analysis is at the level of indexes. However, since each index is composed of the most basic data fields, the existing technology does not have the ability to trace the data source of the index, and cannot query each data field of the data source, resulting in that the user cannot know the data details that constitute each index. SUMMARY

[0003] The present application provides an index link detail analysis method and device based on data blood relationship to solve the technical problem that the original detail data cannot be directly viewed in the existing technology index link penetration process.

[0004] According to an aspect of the present application, an index link detail analysis method based on data blood relationship is provided, comprising:

[0005] receiving a link traceability query task, identifying a target index and an index query condition corresponding to the link traceability query task;

[0006] performing link query in the index processing logic link based on the target index and the index query condition, determining the target processing logic link of the target index;

[0007] iterative blood tracing in the data blood relationship graph based on the target processing logic link and the index query condition, determining the data blood detail information of the target index;

[0008] construct a data bloodline link detail graph corresponding to the link traceability query task based on the data bloodline detail information and the target processing logic link.

[0009] According to another aspect of the present application, there is provided a data bloodline based index link detail analysis device, comprising:

[0010] An index link task module is configured to receive a link traceability query task, and identify a target index and an index query condition corresponding to the link traceability query task.

[0011] A link query module is configured to perform link query in an index processing logic link based on the target index and the index query condition, and determine a target processing logic link of the target index.

[0012] A bloodline tracing module is configured to perform iterative bloodline tracing in a data bloodline relationship graph based on the target processing logic link and the index query condition, and determine data bloodline detail information of the target index.

[0013] A data bloodline link display module is configured to construct a data bloodline link detail graph corresponding to the link traceability query task based on the data bloodline detail information and the target processing logic link.

[0014] According to another aspect of the present application, there is provided an electronic device, comprising:

[0015] at least one processor; and

[0016] a memory communicatively connected to the at least one processor; wherein

[0017] the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the data bloodline based index link detail analysis method according to any one of the embodiments of the present application.

[0018] According to another aspect of the present application, there is provided a computer readable storage medium storing computer instructions for enabling a processor to perform the data bloodline based index link detail analysis method according to any one of the embodiments of the present application.

[0019] The technical scheme of the embodiment of the present application comprises the following steps: receiving a link tracing query task, identifying a target index and an index query condition corresponding to the link tracing query task, setting the index query condition to accurately filter data in the process of index link tracing, and improving the efficiency of data tracing; performing link query in an index processing logic link based on the target index and the index query condition, determining a target processing logic link of the target index, effectively decomposing the index into the most basic atomic index through index link penetration of the index processing logic link, determining index link information, and improving the accuracy of data tracing; performing iterative blood relationship tracing on a data blood relationship graph based on the target processing logic link and the index query condition, determining data blood detailed information of the target index, and directly penetrating the index link to the most original detailed data through iterative blood relationship tracing on the data used to construct the index; and constructing a data blood link detailed graph corresponding to the link tracing query task based on the data blood detailed information and the target processing logic link, displaying the most comprehensive index link and data blood link of the index through the data blood link detailed graph, and supporting the user to view and select each related data of the index link and the blood link. The technical problem of the prior art that the most original detailed data cannot be directly viewed in the index link penetration process is solved. The most source detailed data can be directly viewed and selected in the index link analysis process, greatly increasing the interpretability of the index and improving the analysis efficiency.

[0020] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become apparent from the following description.

[0021] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiment description. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without creative labor.

[0023] Figure 1 A flowchart of an index link detailed analysis method based on data blood relationship is provided for the embodiments of the present application;

[0024] Figure 2 A schematic diagram of a process of blood extraction and column operator reservation provided for the embodiments of the present application;

[0025] Figure 3 A schematic diagram of a data bloodline link details provided for an embodiment of the present application is shown.

[0026] Figure 4 A flowchart of a data bloodline based index link details analysis method provided for an embodiment of the present application is shown.

[0027] Figure 5 A structural schematic diagram of a data bloodline based index link details analysis device provided for an embodiment of the present application is shown.

[0028] Figure 6 A flowchart of a single bloodline tracing task performed by a tracing task group on a single bloodline tracing task provided for an embodiment of the present application is shown.

[0029] Figure 7 A flowchart of each upstream bloodline of a bloodline tracing task being traced separately provided for an embodiment of the present application is shown.

[0030] Figure 8 A structural schematic diagram of an electronic device 10 that can be used to implement an embodiment of the present application is shown. DETAILED DESCRIPTION

[0031] In order to make the personnel in the technical field better understand the present application scheme, the technical scheme in the embodiment of the present application will be described clearly and completely below in combination with the drawings in the embodiment of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by the person skilled in the art without creative labor should belong to the scope of protection of the present application.

[0032] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily have to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0033] Figure 1A flowchart of a data bloodline-based index link detailed analysis method is provided for an embodiment of the present application. The embodiment can be applicable to index bloodline link analysis of indexes. The method can be executed by a data bloodline-based index link detailed analysis device. The data bloodline-based index link detailed analysis device can be realized in the form of hardware and / or software and can be configured in an electronic device. As shown in FIG. 8, the method comprises the following steps. Figure 1

[0034] In S110, a link traceability query task is received, and a target index and an index query condition corresponding to the link traceability query task are identified.

[0035] The link traceability query task can be task data input by a user for bloodline link analysis traceability. It should be noted that the link traceability query task includes a target index for which the user needs to perform bloodline link analysis traceability and an index query condition for setting bloodline link analysis traceability.

[0036] The target index can be an index selected by the user for bloodline link analysis traceability.

[0037] The index query condition can be a data filtering condition for bloodline link analysis traceability. The index query condition can be used to accurately locate the data required for bloodline link analysis traceability. For example, the index query condition can be a time range, a dimension condition, a numerical range, a business label, and index metadata.

[0038] Optionally, in the present application, an interface or page for inputting indexes for bloodline link analysis traceability can be provided to the user. The user can log in to the interface or page, input a target index for index bloodline link analysis traceability in an input control displayed in the interface or page, select or input an index query condition for the analysis target index in a selection control or another input control, and trigger a traceability control provided in the interface or page to generate a link traceability query task.

[0039] Optionally, in order to support bloodline link analysis traceability of indexes, the interface or page is further connected to an index library and a data bloodline library. The indexes and data bloodlines stored in the index library and the data bloodline library are used to perform bloodline link analysis traceability of indexes.

[0040] ​Optionally, the data warehouse is a subject-oriented, integrated, relatively stable, and historical change reflecting data set, and the data warehouse is divided into multiple levels, namely, a source layer, a detail layer, a summary layer, and an application layer. The source layer is directly connected to the data source, and stores raw data without processing, and retains the initial state of the data. The detail layer cleanses, converts, and integrates the data of the source layer, organizes the data according to a subject domain, and provides detailed and standardized data. The summary layer aggregates the data of the detail layer according to business requirements, and generates highly summarized data for a specific subject. The application layer presents the data to the end user and the application system in the form of a report, a chart, or the like, and provides intuitive support for decision-making and business analysis.

[0041] Optionally, the data warehouse in the application can be more than one, and a user can specify any data warehouse as a data source. The application can connect the data warehouse, and update the indicators in the indicator library and the data lineage in the data lineage library based on the data warehouse.

[0042] Optionally, after connecting the data source such as the data warehouse, the application performs ETL (Extract-Transform-Load) operation through an ETL tool, and processes the data of the data source such as the data warehouse.

[0043] Specifically, a link traceability query task input by a user is received, the link traceability query task is identified, and a target indicator that needs to be analyzed by blood lineage link and an indicator query condition for filtering blood data are determined.

[0044] S120, link query is performed in the indicator processing logic link based on the target indicator and the indicator query condition, and a target processing logic link of the target indicator is determined.

[0045] The indicator processing logic link can be a derivative relationship and / or a composite calculation relationship between all indicators stored in the indicator library.

[0046] The target processing logic link can be a logic link that meets the indicator query condition in the indicator processing logic link of the target indicator in the indicator library. It should be noted that in the indicator library, the indicator processing logic link corresponding to the target indicator can include indicators of different types. The indicator processing logic link corresponding to the target indicator is filtered based on the indicator query condition, and indicators meeting the indicator query condition are retained to constitute the target processing logic link of the target indicator.

[0047] Optionally, the complete index library contains the business meaning, dimension information, and the like of various indexes, and the types of indexes are any one of atomic indexes, derived indexes, and composite indexes; the atomic index is the most basic and non-divisible index, used to describe a specific fact in the business process; the derived index is an index derived from an atomic index through certain operations or processing rules. The composite index is an index formed by multiple atomic indexes or derived indexes, or even other composite indexes through complex calculation logic. The index processing logic link is formed through the derivation relationship and / or composite calculation relationship between various indexes.

[0048] Optionally, the index library is obtained by explicitly associating and materializing the index data, calculation logic, and dimensions of the index data mart. It should be noted that the index data mart is a specific type of data mart, a data collection constructed around the user-set key index system, a specific theme domain, and a refined and integrated data collection. The index data mart usually extracts data related to specific business indexes from the user-specified data warehouse and other data sources, and organizes and stores the data according to certain themes and dimensions.

[0049] Specifically, in the index library, link query is performed based on the target index and the index query condition, and the target processing logic link that meets the target index and the index query condition is matched in all the index processing logic links of the index library

[0050] S130, based on the target processing logic link and the index query condition, iteratively tracing the data blood relationship in the data blood relationship graph to determine the data blood detailed information of the target index.

[0051] Among them, the data blood relationship graph can be a graph data describing the data blood relationship between each data. The data blood detailed information can be detailed information corresponding to the dependency relationship and operation logic between all data constituting the target index.

[0052] Optionally, the data blood library stores the data blood of the data. The data blood refers to the origin and relationship chain in the process of data generation, processing, circulation, and the like. The data blood describes the entire path of data from the data source to the final target, including various processing links, conversion operations, and association relationships with other data. Through the data blood relationship, the origin, evolution process of the data, and the dependency relationship between the data can be clearly understood.

[0053] Optionally, the process of data lineage extraction is the process of extracting the dependency relationship between databases, tables, and fields and retaining the operation logic. During data processing and transfer, data is transmitted and converted between different databases, data tables, and fields in the tables. Data lineage extraction needs to clearly record the origin of data from which table in which database, through which intermediate processing steps, and finally into which specific field in which table in the target database. For example, the data in field F1 of table T1 in source database A is processed through the ETL process and stored in field F2 of table T2 in target database B. Data lineage analysis needs to accurately record the complete dependency path from A.T1.F1 to B.T2.F2.

[0054] Optionally, data often undergoes various operations and processing during the transfer process, such as addition, subtraction, multiplication, division, function calculation, data splicing, conditional judgment, etc. Retaining operation logic is to record these specific operation steps and rules so that the data generation process can be accurately restored when needed. For example, the value of a certain field is obtained by adding two other fields and multiplying a fixed coefficient. Data lineage analysis needs to record this specific operation formula and the involved fields.

[0055] Optionally, the implementation of data lineage extraction can be achieved by collecting and analyzing metadata during data processing. By recording each data operation step in the ETL tool or data processing platform, including the database, table, and field information involved in data reading, writing, conversion, etc., the dependency relationship of the data is stored, and the operation rules are recorded in detail in the ETL tool operation configuration. These information is associated with the data lineage relationship and stored, and finally the data lineage relationship graph is formed based on the data dependency relationship and operation logic. Through the data lineage relationship graph, the dependency relationship between data and the operation logic can be displayed. For example, Figure 2 A schematic diagram of the process of extracting lineage and retaining column operators provided by the present application for implementation. As shown in Figure 2 Based on the a1 field in table A, the c1 field in table C is obtained through the column operator a1+10. Based on the above-mentioned SQL statement of the process: INSERT INTO C(c1); SELECT A.a1+10 FROM A, a lineage relationship is extracted.

[0056] Optionally, in the data lineage extraction process, the aggregation operator is ignored. For example: the field in table a is aggregated from the b1 and b2 fields in table b. During the data lineage extraction process, the aggregation operation operator of table b is not retained to ensure that when querying the data details of the field in table a, the upstream details of the field can be seen. b1 and b2 fields in table b without aggregation.

[0057] Optionally, when the target indicator is traced based on the target processing logic link and the index query condition in the data blood relationship diagram, the multiple generations of blood relationship of the data blood of the target indicator need to be iteratively traced to obtain the complete data blood detailed information of the target indicator.

[0058] S140, based on the data blood detailed information and the target processing logic link, a data blood link detailed diagram corresponding to the link traceability query task is constructed.

[0059] It should be noted that the data blood link detailed diagram includes a complete target processing logic link, an index table corresponding to each index, and a data table in the data warehouse having a data blood relationship with each index table. For example, Figure 3 A schematic diagram of the data blood link detailed diagram provided by the embodiment of the application is shown in FIG. 1. Figure 3 As shown in FIG. 1, index D is the target indicator, the index type of index D is a composite index, the upstream of the index link of index D is index C, index C is a derived index, the upstream of the index link of index C is index A and index B, index A and index B are atomic indexes, the data blood upstream of index A is index table A, index A comes from the index field of index table A, the data blood upstream of index B is index table B, index B comes from the index field of index table B, the data blood upstream of index table A is summary table E, the data blood upstream of summary table E is source layer table C; the data blood upstream of index table B is dimension table D and summary table F, the data blood upstream of summary table F is source layer table D.

[0060] Optionally, when the data blood link detailed diagram is displayed, the target processing logic link of the index and the data blood relationship of the index are usually displayed by default, that is, the logical relationship of each index, the logical relationship of the index table, and the logical relationship of the data table are displayed by default.

[0061] Optionally, when the data blood link detailed diagram is displayed by the application, when a user selects to display any data table, only the fields in the data table having a data blood relationship with the target indicator are displayed, and all the fields in the data table are not displayed; when a user selects to display any index table, only at least one index in the index table having a data blood relationship with the target indicator is displayed, and all the index data in the index table are not displayed.

[0062] Specifically, the data blood link detailed diagram corresponding to the link traceability query task is constructed based on the data blood detailed information and the target processing logic link.

[0063] The technical scheme of the embodiment of the present application receives a link traceability query task, identifies a target index and an index query condition corresponding to the link traceability query task, and in the process of index link traceability, the index query condition can be used to accurately filter data and improve the efficiency of data traceability. Based on the target index and the index query condition, link query is performed in the index processing logic link to determine the target processing logic link of the target index. The index link penetration of the index processing logic link can effectively decompose the index into the most basic atomic index, and the index link information can be determined to improve the efficiency of the accuracy of data traceability. Based on the target processing logic link and the index query condition, iterative bloodline tracing is performed in the data bloodline graph to determine the data bloodline detail information of the target index. The iterative bloodline tracing of the data used to construct the index makes the index link penetration directly penetrate to the most original detailed data. Based on the data bloodline detail information and the target processing logic link, a data bloodline link detail graph corresponding to the link traceability query task is constructed. The data bloodline link detail graph can display the most comprehensive index link and data bloodline link of the index, and support the user to view and select each related data of the index link and the bloodline link. The technical problem of the prior art that the most original detailed data cannot be directly viewed in the index link penetration process is solved. In the process of index link analysis, the most source detailed data can be directly viewed and selected, which greatly increases the interpretability of the index and improves the analysis efficiency.

[0064] Figure 4 A flowchart of an index link detail analysis method based on data bloodline provided by the embodiment of the present application, the relationship between the present embodiment and the above-mentioned embodiments is that the process of iterative bloodline tracing is specifically explained. As shown in Figure 4 the method comprises:

[0065] S410, receiving a link traceability query task, identifying a target index and an index query condition corresponding to the link traceability query task.

[0066] S420, based on the target index and the index query condition, performing link query in the index processing logic link to determine the target processing logic link of the target index.

[0067] S430, determining an atomic index set corresponding to the target index based on the target processing logic link.

[0068] The atomic index set includes at least one atomic index.

[0069] Optionally, when the target processing logic link of the target index is obtained, the index types of each index in the target processing logic link are identified based on the target processing logic link, each atomic index constituting the target processing logic link is identified, and the atomic index is added to the atomic index set.

[0070] Specifically, the atomic index set corresponding to the target index is determined based on the target processing logic link.

[0071] S440, based on the index query condition and the data blood relationship graph, an atomic index is constructed blood traceability task, the blood traceability task is set in the preset traceability task group, and the traceability task group and the data blood relationship graph are iterated blood traceability, and the data blood detailed information of the atomic index is determined.

[0072] Optionally, when the target index is subjected to blood link analysis and tracing, the atomic index corresponding to the target index needs to be subjected to blood link analysis and tracing, so as to identify all the data blood detailed information of the target index.

[0073] Wherein, the blood traceability task can be a task information for once blood traceability of an index or a field; it should be noted that the attributes of the blood traceability task are index field list, filtering condition, association condition, whether it can be retraced, and whether it is a original task; the index field list can be a measurement field list bound by the index or the field; the filtering condition can be the physical table corresponding to the index or field query this time, the filtering condition of the field; the association condition can be the association relationship between different physical tables in the index or field query this time; whether it can be retraced can be understood as whether the field or index has upstream blood; whether it is a original task can be described as whether the blood traceability task is a original traceability task.

[0074] Wherein, the data blood detailed information can be the detailed information corresponding to the dependency relationship and operation logic between all data constituting the atomic index.

[0075] Optionally, when an atomic index is subjected to iterative blood traceability, an initial blood traceability task is constructed for the atomic index, the blood traceability task is used as the original traceability task of the atomic index, the index field list is the original index, the filtering condition and the association condition can be generated and filled based on the index query condition field, whether it can be retraced is the default value "yes", and whether it is a original task is the default value "yes".

[0076] Optionally, if an atomic index has two upstream blood index fields, two new blood traceability tasks are generated for the two upstream blood index fields when the blood traceability task corresponding to the atomic index is completed.

[0077] The trace task group can be a task group preset for iterative blood relationship tracing. It should be noted that the trace task group can trace the data of each generation. For example, when the trace task group traces the blood relationship for the first time, the trace task group only has one blood relationship tracing task, i.e., an original trace task. After the trace task group traces the original trace task, two new blood relationship tracing tasks are generated, the new blood relationship tracing tasks are put into the trace task group, and the trace task group establishes a blood relationship between the original trace task and the new blood relationship tracing tasks. The trace task group traces the blood relationship of the two blood relationship tracing tasks. If new blood relationship tracing tasks are generated again after the trace is completed, the new blood relationship tracing tasks are put into the trace task group again to trace the blood relationship, and the iterative blood relationship tracing is performed in this way until there is no new blood relationship tracing task. It is considered that the iterative blood relationship tracing of the atomic index is completed, and the data blood relationship detailed information is obtained.

[0078] Optionally, at each blood relationship tracing, whether each index or field has an upstream blood relationship is identified based on the data blood relationship graph. For the upstream blood relationship field obtained by the atomic index or the trace process: when the blood relationship tracing task of the atomic index or the field is constructed, the blood relationship is searched in the data blood relationship graph based on the index query condition, it is determined whether the atomic index or the field has an upstream blood relationship, and the attribute of whether the blood relationship tracing task can be traced again is set to "yes".

[0079] Specifically, for each atomic index, a blood relationship tracing task is constructed for the atomic index based on the index query condition and the data blood relationship graph, the blood relationship tracing task is set in a preset trace task group, and iterative blood relationship tracing is performed based on the trace task group and the data blood relationship graph to determine the data blood relationship detailed information of the atomic index.

[0080] Optionally, in another optional embodiment of the present application, the iterative blood relationship tracing based on the trace task group and the data blood relationship graph to determine the data blood relationship detailed information of the atomic index comprises:

[0081] When it is detected that the trace task group has the blood relationship tracing task, for each blood relationship tracing task, the blood relationship tracing task is updated based on the physical table field in the blood relationship tracing task and the data blood relationship graph to determine a blood relationship update result.

[0082] In the case where the blood relationship update result indicates that the blood relationship tracing task cannot be traced again, if the physical table field corresponding to the blood relationship tracing task is not the atomic index, the blood relationship tracing task is marked as a completed blood relationship tracing task and stored in the trace task group.

[0083] In the case that there are at least one iteration of the bloodline tracing task in the bloodline update result, all the bloodline tracing tasks are added in the tracing task group, and the step of returning to detect that the tracing task group has the bloodline tracing task is performed, for each bloodline tracing task, bloodline tracing is performed based on the physical table field in the bloodline tracing task and the data bloodline relationship graph to obtain the updated bloodline tracing task until there is no iteration of the bloodline tracing task in the tracing task group.

[0084] The data bloodline detailed information of the atomic index is constructed based on all the bloodline tracing tasks of the tracing task group.

[0085] The bloodline update result can be the result information of the state update of the bloodline tracing task after the bloodline tracing of the bloodline tracing task is completed.

[0086] The physical table field can be a field for which the bloodline tracing task is traced. It should be noted that in the bloodline tracing task corresponding to the index field, the physical table field is the physical table field bound by the index, and in the bloodline tracing task corresponding to the field of the database table, the physical table field is the field of the database table.

[0087] Optionally, in the present application, it is detected in real time whether there is a bloodline tracing task that needs to be traced in the tracing task group, if there is no bloodline tracing task that needs to be traced in the tracing task group, no bloodline tracing is performed, if there is at least one bloodline tracing task that needs to be traced in the tracing task group, the bloodline tracing task is individually traced, after the bloodline tracing of the bloodline tracing task, a bloodline association field in the bloodline tracing task is updated to obtain a bloodline update result corresponding to the bloodline tracing task. The bloodline association field is at least one physical table field corresponding to the upstream bloodline corresponding to the physical table field corresponding to the bloodline tracing task, so as to realize the bloodline association of the bloodline tracing task and the upstream bloodline.

[0088] Optionally, after the bloodline tracing of the bloodline tracing task, if the physical table field corresponding to the bloodline tracing task has no upstream bloodline, it is indicated that the bloodline tracing task no longer needs to be traced in the next generation, the bloodline association field is updated to be no longer traceable, that is, the bloodline tracing result is no longer traceable. The bloodline tracing result being no longer traceable indicates that the bloodline link tracing corresponding to the bloodline tracing task is completed, and the next generation of bloodline tracing is no longer needed, the tracing task group marks the bloodline tracing task as a completed bloodline tracing task, and stores and retains the bloodline tracing task in the tracing task group.

[0089] Optionally, when it is identified that the bloodline tracing task is marked as a completed bloodline tracing task, it is further required to identify whether the physical table field of the bloodline tracing task is an atomic index bound physical table field. If it is an atomic index bound physical table field, it is indicated that the atomic index does not have an upstream bloodline, and the iterative bloodline tracing of the atomic index is directly ended. If it is not an atomic index bound physical table field, it is indicated that the bloodline tracing task is a data bloodline completed by bloodline link tracing, and the bloodline tracing task is stored and reserved in the tracing task group.

[0090] Optionally, after the bloodline tracing task is subjected to bloodline tracing, if the physical table field corresponding to the bloodline tracing task has an upstream bloodline, it is indicated that the bloodline tracing task needs to be subjected to next-generation bloodline tracing, and the bloodline association field is updated to the physical table field corresponding to at least one upstream bloodline, that is, it is indicated that the bloodline tracing task produces a next-generation bloodline tracing task, and the bloodline tracing result is to produce at least one iterative bloodline tracing task.

[0091] Optionally, the number of bloodline tracing results and the number of iterative bloodline tracing tasks are the same as the number of upstream bloodlines, that is, there is one upstream bloodline, and one new bloodline tracing task is produced.

[0092] Optionally, when the bloodline tracing result is to produce at least one iterative bloodline tracing task, all the produced iterative bloodline tracing tasks are added to the tracing task group, the newly produced bloodline tracing tasks are repeatedly subjected to bloodline tracing through the tracing task group, and the step of returning to detecting that the tracing task group has the bloodline tracing task is performed. For each bloodline tracing task, bloodline tracing is performed based on the physical table field in the bloodline tracing task and the data bloodline relationship graph, to obtain an updated bloodline tracing task, until the tracing task group does not have an iterative bloodline tracing task.

[0093] Optionally, when there is no iterative bloodline tracing task in the bloodline update result, it is indicated that the iterative bloodline tracing of the atomic index is completed, all the completed bloodline tracing tasks stored in the tracing task group are read, and the data bloodline detail information of the atomic index is constructed based on the bloodline association field of each bloodline tracing task.

[0094] Specifically, when it is detected that the trace task group exists the bloodline trace task, for each bloodline trace task, the bloodline update is performed on the bloodline trace task based on the physical table field in the bloodline trace task and the data bloodline relationship graph to determine a bloodline update result; in the case that the bloodline trace task is not traceable in the bloodline update result, if the physical table field corresponding to the bloodline trace task is not an atomic index, the bloodline trace task is marked as a completed bloodline trace task and stored in the trace task group; in the case that there is at least one iterative bloodline trace task in the bloodline update result, all the bloodline trace tasks are added in the trace task group, and the step of performing the bloodline trace on each bloodline trace task based on the physical table field in the bloodline trace task and the data bloodline relationship graph to obtain an updated bloodline trace task is returned until there is no iterative bloodline trace task in the trace task group; and the data bloodline detailed information of the atomic index is constructed based on all the bloodline trace tasks in the trace task group.

[0095] Optionally, in another optional embodiment of the present application, the bloodline update performed on the bloodline trace task based on the physical table field in the bloodline trace task and the data bloodline relationship graph to determine a bloodline update result comprises:

[0096] querying the upstream bloodline of the physical table field in the bloodline trace task in the data bloodline relationship graph; if there is at least one upstream bloodline of the physical table field in the bloodline trace task, for each upstream bloodline field corresponding to each upstream bloodline, the bloodline update is performed on the bloodline trace task according to the physical table field and the upstream bloodline field to determine the updated bloodline trace task; and the bloodline update is performed on all the upstream bloodline fields corresponding to all the upstream bloodlines to obtain the bloodline update result.

[0097] wherein the upstream bloodline field is the physical table field corresponding to the upstream bloodline.

[0098] Specifically, for each bloodline tracing task, the upstream bloodline of the physical table field in the bloodline tracing task is queried through the data bloodline graph during bloodline tracing. If there is no upstream bloodline in the bloodline tracing task, it means that the next generation bloodline tracing is no longer needed for the bloodline tracing task, and the bloodline association field is updated to be no longer traceable, i.e., the bloodline tracing result is no longer traceable. If there is at least one upstream bloodline for the physical table field in the bloodline tracing task, and for each upstream bloodline field corresponding to one upstream bloodline, bloodline tracing is performed based on the physical table field and each upstream bloodline field corresponding to the upstream bloodline, the bloodline of the bloodline tracing task is updated, each upstream bloodline field corresponding to one upstream bloodline is updated to the bloodline association field, the updated bloodline tracing task is determined, and the iterative bloodline tracing task corresponding to the upstream bloodline field is output. After the bloodline update of all upstream bloodline fields corresponding to the upstream bloodline is completed, the bloodline update result is obtained.

[0099] Optionally, in the embodiment of the application, the bloodline update of the bloodline tracing task based on the physical table field and the upstream bloodline field to determine the updated bloodline tracing task comprises:

[0100] field conversion, query condition conversion and association condition conversion of the bloodline tracing task based on the physical table field and the upstream bloodline field to determine the updated bloodline tracing task;

[0101] constructing the database bloodline statement corresponding to the bloodline tracing task based on the updated bloodline tracing task;

[0102] if the database bloodline statement is a legal statement, querying whether there is a bloodline tracing task with an upstream bloodline field in the tracing task group;

[0103] if there is no bloodline tracing task with an upstream bloodline field in the tracing task group, generating an iterative bloodline tracing task for the upstream bloodline field based on the bloodline tracing task.

[0104] The field conversion can be converting the physical table field of the bloodline tracing task into an upstream bloodline field group. It should be noted that the number of fields can change during the field conversion, and only the details of the determined physical table field and the upstream bloodline field are displayed during the conversion. For example, the field conversion can be: insert into B(val,dty)select a.value as val,substr(dt)as dty from T1 a; the current task traces the val field of the B table, and traces the value field of the T1 table after one layer of tracing; insert into B(val,dty)select a.value*100as val,substr(dt)as dty from T1 a; the current task traces the val field of the B table, and traces the value field of the T1 table after one layer of tracing, ignores the constant operation, and restores the original value of T1.

[0105] The query condition conversion can be a process of converting the filtering condition of the bloodline tracing task to the upstream bloodline field. For example, in one case, insert into B(val,dty)select a.value as val,substr(dt)as dty from T1 where status=1; the current task traces the val field of the B table without any condition, and traces the value field of the T1 table after one layer of tracing, and brings the condition status=1; insert into B(val,dty)select a.value as val,substr(dt)as dty from T1 where status=1; the current task traces the val field of the B table, dty='2023', and traces the value field of the T1 table after one layer of tracing, and brings the condition status=1 and substr(dt)='2023'.

[0106] The association condition conversion can be converting the association condition of the bloodline tracing task to an upstream bloodline field. For example, in one case of the present application, the index dimension comes from different tables, and the association condition is on the column operator of the table. In this case, the association condition needs to be supplemented in the bloodline tracing task. For example, insert into B(val) select a.value+b.value as val from T1a inner join T2 b on a.dt=b.dt. The current task traces the val field of the B table. Since the source is a two-table association, it is divided into two, one of which traces the value field of the T1 table, and the other traces the value field of the T2 table.

[0107] The database bloodline statement can be a SQL (Structured Query Language) statement generated based on the field conversion, the query condition conversion, and the association condition conversion of the bloodline tracing task.

[0108] Optionally, in the present application, the bloodline tracing task can be directly converted into a corresponding sql statement. After the bloodline tracing task is updated, the updated bloodline tracing task is determined, and the database bloodline statement is directly converted based on the updated bloodline tracing task.

[0109] Optionally, after the bloodline tracing task is converted into the database bloodline statement, it is determined whether the database bloodline statement is a legal SQL statement. If the database bloodline statement is a legal statement, it is determined whether there is a bloodline tracing task with an upstream bloodline field in the tracing task group. If there is no bloodline tracing task with an upstream bloodline field in the tracing task group, it is determined that the upstream bloodline field needs to be traced. An iterative bloodline tracing task is generated for the upstream bloodline field based on the bloodline tracing task.

[0110] Specifically, the bloodline tracing task is converted in terms of the field, the query condition, and the association condition based on the physical table field and the upstream bloodline field, and the updated bloodline tracing task is determined. The database bloodline statement corresponding to the bloodline tracing task is constructed based on the updated bloodline tracing task. If the database bloodline statement is a legal statement, it is determined whether there is a bloodline tracing task with an upstream bloodline field in the tracing task group. If there is no bloodline tracing task with an upstream bloodline field in the tracing task group, an iterative bloodline tracing task is generated for the upstream bloodline field based on the bloodline tracing task.

[0111] Optionally, in another optional embodiment of the present application, if the database blood relation statement is an illegal statement, no iterative blood relation tracing task is generated; if there is a blood relation tracing task with an upstream blood relation field in the tracing task group, no iterative blood relation tracing task is generated.

[0112] Optionally, if the database blood relation statement is an illegal statement, it indicates that the blood relation tracing of the blood relation tracing task fails, the blood relation tracing task needs to be stopped, the blood relation tracing of the blood relation tracing task is abandoned, and no iterative blood relation tracing task is generated for the upstream blood relation field.

[0113] Optionally, if the database blood relation statement is a legal statement, it is queried in the tracing task group whether there is a blood relation tracing task with an upstream blood relation field. If there is a blood relation tracing task with an upstream blood relation field in the tracing task group, it indicates that there is a loop in the blood relation tracing, and the upstream blood relation field has been traced. Therefore, no iterative blood relation tracing task needs to be generated.

[0114] Optionally, in another optional embodiment of the present application, the data blood relation detailed information of the atomic index is constructed based on all blood relation tracing tasks of the tracing task group, including: reading each blood relation tracing task in the tracing task group in sequence, and identifying the blood relation associated field of each blood relation tracing task; and constructing the data blood relation detailed information of the atomic index based on the blood relation associated field of each blood relation tracing task.

[0115] Specifically, when there is no iterative blood relation tracing task in the tracing task group, it indicates that the blood relation tracing of the atomic index has been completed. Each completed blood relation tracing task in the tracing task group is read in sequence, the blood relation associated field of the completed blood relation tracing task is identified, the data blood relation detailed information of all blood relation tracing tasks in the tracing task group is constructed through the corresponding blood relation of the blood relation associated field, and the data blood relation detailed information of the atomic index is obtained.

[0116] S450, the data blood relation detailed information of all atomic indexes is summarized to determine the data blood relation detailed information of the target index.

[0117] Specifically, after the blood relation tracing of each atomic index is completed, the data blood relation detailed information of all atomic indexes is summarized to obtain the data blood relation detailed information of the target index.

[0118] S460, based on the data blood relation detailed information and the target processing logic link, a data blood relation link detailed graph corresponding to the link traceability query task is constructed.

[0119] The technical scheme of the embodiment of the present application receives a link traceability query task, identifies a target index and an index query condition corresponding to the link traceability query task, and in the process of index link traceability, the index query condition can be used to accurately filter data and improve the efficiency of data traceability. Link query is performed in the index processing logic link based on the target index and the index query condition, the target processing logic link of the target index is determined, the index can be effectively decomposed into the most basic atomic index through the index link penetration of the index processing logic link, the index link information can be determined, and the efficiency of the accuracy of data traceability is improved. Iterative blood relationship tracing is performed in the data blood relationship graph based on the target processing logic link and the index query condition, the data blood detailed information of the target index is determined, the index link penetration can directly penetrate into the most original detailed data by performing iterative blood relationship tracing on the data used to construct the index, and the data blood link detailed graph corresponding to the link traceability query task is constructed based on the data blood detailed information and the target processing logic link. The index link and the data blood link can be displayed in the data blood link detailed graph, the user can view and select each related data of the index link and the blood link, and the technical problem of the prior art that the most original detailed data cannot be directly viewed in the index link penetration process is solved. In the process of index link analysis, the most source detailed data can be directly viewed and selected, the interpretability of the index is greatly increased, and the analysis efficiency is improved.

[0120] Figure 5 A structural schematic diagram of an index link detailed analysis device based on data blood relationship provided by the embodiment of the present application is shown in FIG. 5. Figure 5 As shown in the figure, the device comprises an index link task module 510, a link query module 520, a blood relationship tracing module 530, and a data blood link display module 540.

[0121] The index link task module 510 is configured to receive a link traceability query task, and identify a target index and an index query condition corresponding to the link traceability query task.

[0122] The link query module 520 is configured to perform link query in the index processing logic link based on the target index and the index query condition, and determine the target processing logic link of the target index.

[0123] The blood relationship tracing module 530 is configured to perform iterative blood relationship tracing in the data blood relationship graph based on the target processing logic link and the index query condition, and determine the data blood detailed information of the target index.

[0124] The data blood relationship link display module 540 is configured to construct a data blood relationship link detail graph corresponding to the link traceability query task based on the data blood relationship detail information and the target processing logic link.

[0125] The technical scheme of the embodiment of the present application receives a link traceability query task, identifies a target index and an index query condition corresponding to the link traceability query task, and in the process of index link traceability, the index query condition can be used to accurately filter data and improve the efficiency of data traceability. The link is queried in the index processing logic link based on the target index and the index query condition, the target processing logic link of the target index is determined, the index link penetration of the index processing logic link can effectively decompose the index into the most basic atomic index, the index link information can be determined, and the efficiency of the accuracy of data traceability is improved. The data blood relationship detail information of the target index is determined by iteratively tracing the blood relationship based on the target processing logic link and the index query condition in the data blood relationship graph. The index link penetration can directly penetrate into the most original detailed data by iteratively tracing the blood relationship of the data used to construct the index. The data blood relationship link detail graph corresponding to the link traceability query task is constructed based on the data blood relationship detail information and the target processing logic link. The index link and the data blood relationship link of the index can be displayed in the data blood relationship link detail graph, and the user can view and select each related data of the index link and the blood relationship link. The technical problem of the prior art that the most original detailed data cannot be directly viewed in the index link penetration process is solved. In the process of index link analysis, the most source detailed data can be directly viewed and selected, which greatly increases the interpretability of the index and improves the analysis efficiency.

[0126] Optionally, the blood relationship tracing module 530 is specifically configured to:

[0127] The target processing logic link is used to determine an atomic index set corresponding to the target index, and the atomic index set includes at least one atomic index.

[0128] For each atomic index, the blood relationship tracing task is constructed for the atomic index based on the index query condition and the data blood relationship graph, the blood relationship tracing task is set in a preset tracing task group, and the data blood relationship detail information of the atomic index is determined by iteratively tracing the blood relationship based on the tracing task group and the data blood relationship graph.

[0129] The data blood relationship detail information of all the atomic indexes is summarized to determine the data blood relationship detail information of the target index.

[0130] Optionally, the blood relationship tracing module 530 is specifically configured to:

[0131] When it is detected that the trace task group has the bloodline trace task, for each bloodline trace task, bloodline update is performed on the bloodline trace task based on a physical table field in the bloodline trace task and the data bloodline relationship graph, and a bloodline update result is determined;

[0132] When the bloodline update result has a case that the bloodline trace task is not traceable again, if the physical table field corresponding to the bloodline trace task is not the atomic index, the bloodline trace task is marked as a completed bloodline trace task, and is stored in the trace task group;

[0133] When the bloodline update result has a case that at least one iteration of the bloodline trace task is output, all the bloodline trace tasks are added in the trace task group, and the step of detecting that the trace task group has the bloodline trace task is returned, for each bloodline trace task, bloodline trace is performed based on a physical table field in the bloodline trace task and the data bloodline relationship graph, and the updated bloodline trace task is obtained, until the trace task group does not have the iteration of the bloodline trace task;

[0134] Based on all the bloodline trace tasks of the trace task group, data bloodline detailed information of the atomic index is constructed.

[0135] Optionally, the bloodline trace module 530 is specifically further configured to:

[0136] In the data bloodline relationship graph, an upstream bloodline of the physical table field in the bloodline trace task is queried;

[0137] If the physical table field in the bloodline trace task has at least one upstream bloodline, for each upstream bloodline field corresponding to the upstream bloodline, bloodline update is performed on the bloodline trace task according to the physical table field and the upstream bloodline field, and the updated bloodline trace task is determined;

[0138] All the upstream bloodline fields corresponding to the upstream bloodlines complete the bloodline update, and the bloodline update result is obtained.

[0139] Optionally, the bloodline trace module 530 is specifically further configured to:

[0140] The bloodline trace task is converted according to the physical table field and the upstream bloodline field, a query condition is converted, an association condition is converted, and the updated bloodline trace task is determined;

[0141] Based on the updated bloodline trace task, a database bloodline statement corresponding to the bloodline trace task is constructed;

[0142] If the database blood relationship statement is a legal statement, it is queried in the trace task group whether there is a blood relationship trace task with an upstream blood relationship field;

[0143] If there is no blood relationship trace task with an upstream blood relationship field in the trace task group, an iterative blood relationship trace task is generated for the upstream blood relationship field based on the blood relationship trace task.

[0144] Optionally, the blood relationship trace module 530 is further used for:

[0145] If the database blood relationship statement is an illegal statement, no iterative blood relationship trace task is generated.

[0146] If there is a blood relationship trace task with an upstream blood relationship field in the trace task group, no iterative blood relationship trace task is generated.

[0147] Optionally, the blood relationship trace module 530 is further used for:

[0148] Each blood relationship trace task in the trace task group is read in turn, and a blood relationship association field of each blood relationship trace task is identified.

[0149] Data blood relationship detailed information of the atomic index is constructed based on the blood relationship association field of each blood relationship trace task.

[0150] The data blood relationship-based index link detailed analysis device provided in the embodiments of the present application can execute the data blood relationship-based index link detailed analysis method provided in any of the embodiments of the present application, and has the corresponding function modules and beneficial effects of the execution method.

[0151] Figure 6 A process schematic diagram of a trace task group performing blood relationship trace on a single blood relationship trace task is provided in the embodiments of the present application. Figure 6 The process schematic diagram comprises the following steps:

[0152] S610, the trace task group acquires a single blood relationship trace task.

[0153] S620, the attribute of the single blood relationship trace task is queried. Specifically, the trace task group acquires the attribute of the single blood relationship trace task, and identifies attribute information of an index field list, a filtering condition, an association condition, whether it can be traced again, and whether it is an original task.

[0154] S630, query whether the bloodline tracing task has an upstream bloodline. Specifically, the bloodline relationship of the physical table field of the bloodline tracing task is queried in the data bloodline relationship graph to identify whether the physical table field of the bloodline tracing task has an upstream bloodline. If the bloodline tracing task has at least one upstream bloodline, step S640 is performed; if the bloodline tracing task has no upstream bloodline, step S650 is performed.

[0155] S640, individually trace each upstream bloodline.

[0156] S650, mark the bloodline tracing task as a non-traceable state. Specifically, the bloodline tracing task is marked as a completed bloodline tracing task in the tracing task group.

[0157] S660, identify whether the bloodline tracing task has an iterative bloodline tracing task. If there is an iterative bloodline tracing task, step S670 is performed; if there is no iterative bloodline tracing task, step S650 is performed.

[0158] S670, update the tracing task group. Specifically, all the newly generated bloodline tracing tasks are added to the tracing task group of the next round of iteration.

[0159] S680, identify the properties of the bloodline tracing task in the non-traceable state, and identify whether the bloodline tracing task in the non-traceable state is the original tracing task. If the bloodline tracing task in the non-traceable state is not the original tracing task, step S690 is performed; if the bloodline tracing task in the non-traceable state is the original tracing task, step S6100 is performed.

[0160] S690, store the bloodline tracing task in the tracing task group.

[0161] S6100, end the bloodline tracing of the original tracing task by the tracing task group.

[0162] Optionally, Figure 7 a flowchart for individually tracing each upstream bloodline of the bloodline tracing task is provided for the embodiments of the present application; as shown in Figure 7

[0163] S710, perform field conversion, query condition conversion and association condition conversion on the bloodline tracing task based on the upstream bloodline field of the upstream bloodline.

[0164] S720, construct a database bloodline statement, and determine whether the database bloodline statement is a legal statement. If the database bloodline statement is a legal SQL statement, step S730 is performed; if the database bloodline statement is not a legal SQL statement, step S740 is performed.

[0165] ​S730, whether a table in the bloodline tracing process appears. If yes, S740 is executed; if not, S750 is executed.

[0166] S740, the iterative bloodline tracing task is not output. Specifically, if the table in the bloodline tracing process appears, it indicates that there is a loop in the bloodline tracing, and the upstream bloodline field has been traced.

[0167] S750, the iterative bloodline tracing task is output.

[0168] The technical scheme of the embodiment of the present application solves the technical problem that in the prior art, the most original detailed data cannot be directly viewed in the index link penetration process. It is achieved that in the index link analysis process, the detailed conditions of the source of the selected data can be directly viewed, the interpretability of the index is greatly increased, and the analysis efficiency is improved.

[0169] Figure 8 A structural schematic diagram of an electronic device 10 that can be used to implement embodiments of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, tablets, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices (e.g., headsets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their modes of operation, are meant to be examples only, and are not intended to limit the implementations of the present application described and / or claimed in this document.

[0170] As shown in Figure 8 The electronic device 10 includes at least one processor 11, and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., which is communicatively connected to the at least one processor 11, wherein the memory stores a computer program that can be executed by the at least one processor. The processor 11 can execute various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0171] A plurality of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer grid, such as the Internet, and / or various telecommunication grids.

[0172] The processor 11 can be various general and / or special purpose processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 performs various methods and processes described above, such as the data lineage-based metric link detail analysis method.

[0173] In some embodiments, the data lineage-based metric link detail analysis method can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded onto the RAM 13 and executed by the processor 11, one or more steps of the data lineage-based metric link detail analysis method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the data lineage-based metric link detail analysis method by any other appropriate means, such as by means of firmware.

[0174] Various implementations of the systems and techniques described above can be realized in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0175] Computer programs for implementing the methods of the present application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer program when executed by the processor implements the methods / operations specified in the flow charts and / or block diagrams. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine as a stand-alone software package and partially on a remote machine or entirely on a remote machine or server.

[0176] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of a machine-readable storage medium will include one or more lines of a program of instructions in a transitory signal, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0177] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0178] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by 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), a blockchain network, and the Internet.

[0179] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. A server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.

[0180] It should be understood that the various forms of flow shown above can be reordered, added to, or deleted from without departing from the scope of the present application. For example, the steps described in the present application can be executed in parallel, in sequence, or in a different order, as long as the desired results of the technical solutions of the present application can be achieved, and the present application is not limited herein.

[0181] The embodiment provides a computer readable storage medium, which stores a computer program, and the program is executed by a processor to implement a data blood relationship-based index link detail analysis method provided by any embodiment of the present application, the method comprises the following steps:

[0182] Receiving a link tracing query task, identifying a target index and an index query condition corresponding to the link tracing query task;

[0183] Performing link query in an index processing logic link based on the target index and the index query condition, and determining a target processing logic link of the target index;

[0184] Based on the target processing logic link and the index query condition, performing iterative blood relationship tracing in a data blood relationship graph to determine data blood relationship detail information of the target index;

[0185] Based on the data blood relationship detail information and the target processing logic link, constructing a data blood relationship link detail graph corresponding to the link tracing query task.

[0186] The computer storage media of embodiments of the present application can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired computer program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, or twisted pair, then the coaxial cable, fiber optic cable, or twisted pair are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and Blu-Ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.

[0187] In addition to storage on computer readable medium, instructions and / or data for the present application can be provided on transient signals. Such signals can be in the form of, for example, data packets, user-equivalent signals, user-equivalent carrier waves, infrared signals, digital or analog communications, or the like, including combinations thereof.

[0188] The software from such computer-readable medium or computer-readable storage medium can be installed onto a computer, either using an installation package or other installation techniques, such as from a server using the software. The software can be installed into a computer using any known or future developed installation techniques, including but not limited to, using an installation package, or other installation techniques, such as from a server using the software.

[0189] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object-oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can 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 the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). The application program code can be downloaded to a remote or local computer or server from a computer program product, which can be a computer readable medium having a computer readable program code embodied therein.

[0190] Those of ordinary skill in the art will appreciate that the various modules or steps of the application described above can be implemented with general computing devices, which can be centralized on a single computing device or distributed across a grid of multiple computing devices, and optionally, they can be implemented with computer device executable program code, which can be stored in a storage device and executed by a computing device, or they can be fabricated as individual integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the application is not limited to any particular combination of hardware and software.

[0191] It should be understood that the various forms of flow illustrated above can be reordered, steps added or deleted. For example, the various steps described in the application can be performed in parallel, in series, or in a different order, as long as the desired results of the technical solutions of the application are achieved, which are not limited herein.

[0192] The above detailed description does not constitute a limitation on the protection scope of the application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of the application shall be included in the protection scope of the application.

Claims

1. A method for analyzing details of an index link based on data bloodlines, characterized in that, The method comprises: receiving a link tracing query task, identifying a target index corresponding to the link tracing query task and an index query condition; performing link query in an index processing logic link based on the target index and the index query condition, determining a target processing logic link of the target index; based on the target processing logic link and the index query condition, performing iterative blood relationship tracing in a data blood relationship graph to determine data blood detailed information of the target index; based on the data blood detailed information and the target processing logic link, constructing a data blood link detailed graph corresponding to the link tracing query task.

2. The method of claim 1, wherein, The method comprises: based on the target processing logic link, determining an atomic index set corresponding to the target index; wherein the atomic index set comprises at least one atomic index; for each atomic index, based on the index query condition and the data blood relationship graph, constructing a blood tracing task for the atomic index, setting the blood tracing task in a preset tracing task group, and based on the tracing task group and the data blood relationship graph, performing iterative blood tracing to determine data blood detailed information of the atomic index; summarizing the data blood detailed information of all the atomic indexes to determine the data blood detailed information of the target index.

3. The method of claim 2, wherein, The method comprises: when the tracing task group contains the blood tracing task, for each blood tracing task, based on the physical table field in the blood tracing task and the data blood relationship graph, updating the blood of the blood tracing task, and determining the blood update result; if the physical table field corresponding to the blood tracing task is not the atomic index, the blood tracing task is marked as a completed blood tracing task and stored in the tracing task group when the blood update result contains the blood tracing task that cannot be traced again; when the blood update result contains at least one iterative blood tracing task, all the blood tracing tasks are added to the tracing task group, and the step of detecting the blood tracing task in the tracing task group is returned, for each blood tracing task, based on the physical table field in the blood tracing task and the data blood relationship graph, blood tracing is performed to obtain the updated blood tracing task until the tracing task group does not contain iterative blood tracing task; based on all the blood tracing tasks of the tracing task group, the data blood detailed information of the atomic index is constructed.

4. The method of claim 3, wherein, The method comprises: querying the upstream blood in the data blood relationship graph for the physical table field in the blood tracing task; If at least one upstream blood relationship exists in a physical table field in the blood relationship tracing task, for each upstream blood relationship field corresponding to the upstream blood relationship, blood relationship updating is performed on the blood relationship tracing task according to the physical table field and the upstream blood relationship field, and an updated blood relationship tracing task is determined; After blood relationship updating is completed on all upstream blood relationship fields corresponding to the upstream blood relationship, blood relationship updating results are obtained.

5. The method of claim 4, wherein, The blood relationship updating performed on the blood relationship tracing task according to the physical table field and the upstream blood relationship field includes: Field conversion, query condition conversion and association condition conversion are performed on the blood relationship tracing task according to the physical table field and the upstream blood relationship field, and an updated blood relationship tracing task is determined; A database blood relationship statement corresponding to the blood relationship tracing task is constructed based on the updated blood relationship tracing task; If the database blood relationship statement is a legal statement, it is queried in the tracing task group whether there is a blood relationship tracing task with an upstream blood relationship field; If there is no blood relationship tracing task with an upstream blood relationship field in the tracing task group, an iterative blood relationship tracing task is generated for the upstream blood relationship field based on the blood relationship tracing task.

6. The method according to claim 5, characterized in that, Further comprising: If the database blood relationship statement is an illegal statement, no iterative blood relationship tracing task is generated; If there is a blood relationship tracing task with an upstream blood relationship field in the tracing task group, no iterative blood relationship tracing task is generated.

7. The method of claim 3, wherein, Based on all blood relationship tracing tasks in the tracing task group, data blood relationship detailed information of an atomic index is constructed, including: Each blood relationship tracing task in the tracing task group is read in sequence, and blood relationship association fields of each blood relationship tracing task are identified; Based on the blood relationship association fields of each blood relationship tracing task, data blood relationship detailed information of the atomic index is constructed.

8. A data bloodline-based index link detail analysis device, characterized by, Comprising: An index link task module is configured to receive a link traceability query task, and identify a target index and an index query condition corresponding to the link traceability query task; A link query module is configured to perform link query in an index processing logic link based on the target index and the index query condition, and determine a target processing logic link of the target index; A blood relationship tracing module is configured to perform iterative blood relationship tracing in a data blood relationship graph based on the target processing logic link and the index query condition, and determine data blood relationship detailed information of the target index; A data blood relationship link display module is configured to construct a data blood relationship link detailed graph corresponding to the link traceability query task based on the data blood relationship detailed information and the target processing logic link.

9. An electronic device, comprising: The electronic device comprises: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the data blood relationship-based index link detailed analysis method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for causing the processor to implement the data bloodline-based index link detail analysis method in any one of claims 1-7 when executed.

Images