Configure the lineage graph to specify data granularity, control the type of assets that you see, apply business context through overlays, and simplify complex flows using filters. Use the configuration hub to customize the lineage graph for specific governance or technical analysis requirements.
To access the configuration hub, click the Manage Configuration icon from the lineage toolbar on the top of the page. The configuration hub lets you select data lineage levels, apply filters and overlays, and add rules to control the assets you see in the lineage. After you select your preferred configuration options from the hub, click Apply at the bottom of the hub for the changes to take effect on the lineage canvas.
The following image highlights the lineage configuration menu on the Lineage page of a sample technical asset:
The Manage Configuration hub provides the following configuration options for your lineage:
Data lineage levels
Based on the granularity of the data that you want to see in your lineage, you can choose to view data lineage at the following levels:
•Catalog source. The highest lineage level that you can see for technical data sets. At this level, the data flows from one catalog source to another, with the lineage aggregating data from the data element or data set level.
•System. The highest lineage level that you can see for system assets and business data sets. At this level, the data flows from one source system to another, with the lineage aggregating data from the data set level.
•Data Set. A high level lineage that shows how data flows from one technical or business data set to another without drilling down to the constituent data element level in the data flow. For example, an Oracle table, an SQL table, and an Amazon S3 flat file are all considered technical data sets.
•Data Element. A granular level lineage that displays how the data elements belonging to a technical data set are involved in the data flow, how data flows from source to destination, and how the data is transformed.
You can switch from one lineage level to another to define the granularity of data that you want to see in the lineage. When you switch from a data set level lineage to a data element level lineage, you can select, from the preview pane, specific data elements to include in the lineage.
The following image shows the preview pane for selecting one or more data elements to include in the lineage when you switch from data set level to data element level lineage:
Filters
Use filters to focus on specific assets within the lineage. You can apply the following quick filters and rules on your lineage:
•Hide data process. You can apply this filter only for technical assets while viewing the technical lineage. Use this option to hide all data processes in a lineage to simplify complex lineage visualizations. Data process in a lineage refers to objects that perform transformations or other operations on data. For example, data process objects include mapping tasks, mapping task instances, stored procedures, ELT pipelines, and so on.
If you apply this filter, you might see fewer nodes in the lineage. Additionally, if you expand the lineage by a single hop and the adjacent hop is a data process node, then the expansion might not display any new hops until you expand subsequent hops in the lineage.
•Hide reference assets. You can apply this filter only for technical assets while viewing the technical lineage. Use this option to hide all assets from reference catalog sources.
•Add Rules For Asset Preferences. In addition to the quick filters, you can create advanced rules to show or hide assets in the lineage based on criteria such as asset name, asset type, and lifecycle status of the assets. You can combine multiple conditions in a single rule using the AND logic, or combine multiple rules using the OR logic to precisely define the scope of your lineage.
The following image shows the rule builder where you can define asset preferences:
Flow lines
Select one of the following options:
•Enable all flow lines for attributes. View data flow across all data elements in the lineage.
•Enable loops. Remove repeated assets and repeated paths in the data flow so that you can see the relationships in loops in the lineage. This option shows cyclic relationships and repeated paths within the data flow.
Overlays
Apply overlays to add business and technical context to the assets in a lineage. Overlays are grouped into different categories, such as Glossary, Business Impact, Data Quality and Tags. The Glossary, Business Impact and Data Quality overlays are displayed as individual groups on the lineage. The overlays in the Tags category are displayed as inline overlays within each asset node.
When you apply the Business Term or Metric overlay, you can identify business terms or metrics marked as critical data elements by the Critical Data Element (CDE) icon next to them. In the overlay, all glossaries containing CDEs appear first, followed by non-CDE glossaries. Within each category, the glossaries are sorted alphabetically.
If the Data Marketplace Administrator has connected Data Marketplace to Data Governance and Catalog, the Overlays menu displays the Data Marketplace overlay. You can use the Data Marketplace overlay to see the assets that are added to one or more data collections in Data Marketplace, including the assets that are added to unpublished data collections.
You can apply the Sensitivity overlay to display icons depicting the sensitivity of data elements on the asset node. The color of the sensitivity icon varies based on the sensitivity level.
If a data element is associated with any data element classification and glossary assets, you can view the details of the data element classifications and the associated glossary assets when you hover over the Sensitivity and Calculation Expression icons.
