- Data lineage applies upstream in the data flow. It refers to as a reverse lineage question, such as asking where the information comes from.
- Data impact applies downstream in the data flow. It refers to as a forward lineage question, such as asking what will be impacted by a change.
- Full data lineage applies both upstream and downstreamn in the data flow. It refers to the two previous types simultaneously.
- You may invoke a lineage and/or impact trace by going to the Data Flow tab or context menu from a classifier (table, file, entity, and so on) or feature (column, field, attribute, and so on) which will present an end-to-end trace across all the models and mappings in your current configuration.
- You may invoke a lineage overview by going to the Data Flow tab from the detail page for a model, schema, ETL job, BI design, and so on, which will present lineage within the model, even without stitching them to other models.
A data flow lineage trace presents summary lineage as opposed to the data flow overview lineage which presents detailed transformation lineage. When you trace impact or lineage of a table or column, you do not see all the transformations. Instead, you see a summary of the whole job.
Constants are not displayed on the lineage diagram. If a constant appears as a source for lineage and the process only has that constant as a source for a lineage trace, you will not see that process in the lineage trace.