Skip to main content Skip to complementary content

Data lineage

Data lineage shows the data flow from the data destination (output component), through various components and stages, to the data source (input component). The data lineage results trace the life cycle of the data flow between different components, including the operations that are performed upon the data.

The example below shows the data lineage made on a database connection item stored under the Metadata node in the Repository tree view.

To launch a data lineage on a metadata item, complete the following:

Procedure

  1. In the Repository tree view, expand Metadata > Db Connection and then expand the database connection you want to analyze, mysql in this example.
  2. Right-click the centralized table schema of which you want to analyze the life cycle of the data flow, employees in this example.
    The Impact Analysis view displays the Jobs that use the selected table schema. The names of the selected database connection and table schema are displayed in the corresponding fields.
    Impact Analysis view.
  3. From the Column list, select the column name for which you want to analyze the data flow from the data destination (output component), through various components and stages, to the data source (input component). The column to be analyzed in this example is called Name.
    You can skip this step by right-clicking the column Name in the Repository tree view and selecting Impact Analysis from the contextual menu.
  4. Click Data Lineage.
    A bar appears to indicate the progress of the analysis operation and the analysis results are displayed in the view.
  5. Right-click a listed Job and select Open Job from the contextual menu.
    The Job opens in the design workspace.
    Analysis results in the Impact Analysis view.
    The data lineage results trace backward the components and transformations the data in the output column Name passes through before being written in this column.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!