The Lineage tab displays the relationships between a node and other nodes. You can view the node dependencies and the lineage parsed from the code of the node.
Dependencies
The Dependencies graph shows the dependencies of the current node based on its scheduling configuration. You can use this graph to verify that the dependencies are configured correctly. If not, you can return to the scheduling configuration page to reconfigure them. In the Lineage panel, the Dependencies graph displays a data dependency chain of three ODPS_SQL nodes: ods_log_info_d (ODPS_SQL) → dw_user_info_all_d (ODPS_SQL) → rpt_user_info_d (ODPS_SQL). Data flows from the ODS layer to the DW layer and then to the RPT layer.
Lineage
The lineage is parsed based on the code of the current node. For example, an ODPS SQL node contains the following SQL statements:
INSERT OVERWRITE TABLE dw_user_info_all_d PARTITION (dt='${bdp.system.bizdate}')
SELECT COALESCE(a.uid, b.uid) AS uid
, b.gender
, b.age_range
, b.zodiac
, a.region
, a.device
, a.identity
, a.method
, a.url
, a.referer
, a.time
FROM (
SELECT *
FROM ods_log_info_d
WHERE dt = ${bdp.system.bizdate}
) a
LEFT OUTER JOIN (
SELECT *
FROM ods_user_info_d
WHERE dt = ${bdp.system.bizdate}
) b
ON a.uid = b.uid;Based on the preceding SQL statement, the system generates a lineage view. This view identifies dw_user_info_all_d as the output table from a JOIN operation involving ods_log_info_d, illustrating the lineage between the tables.