Skip to main content

​
Lineage

Lineage settings control what a user sees the first time they open a lineage graph, before they zoom, expand, or filter it manually. Because lineage graphs can grow very large, these defaults balance two things:
  • Showing enough context
  • Keeping the graph readable and fast to load
Tune them if users on your instance routinely have to expand the graph manually to see the hops or layer they care about.
The Lineage tab on an asset’s details page has its own Lineage Config control (Settings icon) for Upstream/Downstream Depth and Nodes per layer. That control only changes your current view — it isn’t saved anywhere and resets to the default configured on this page the next time anyone opens a lineage graph. Change the setting on this page instead if you want the new defaults to apply for every user, every time.
To configure the default Lineage view, follow the steps below:
  1. Navigate to Settings > Preferences > Lineage. Lineage settings
  2. Set the following fields:
    • Upstream Depth: Number of upstream hops shown by default when opening a lineage graph, to identify parent-level sources. Default: 2 (range 1–5).
    • Downstream Depth: Number of downstream hops shown by default when opening a lineage graph, to identify child-level targets. Default: 2 (range 1–5).
    • Lineage Layer: Which layer of data relationships loads by default:
      • Entity Lineage: Higher-level connections between entities (default).
      • Column Level Lineage: Relationships between individual columns.
      • Data Observability: Data quality and monitoring insights layered onto the graph.
    • Pipeline View Mode: How pipelines render on the lineage graph:
      • Node: Pipelines appear as their own nodes, showing more detail on data flow through each pipeline (default).
      • Edge: Pipelines appear as direct connections between nodes, for a simpler view.
    Edit Lineage Configuration form
  3. Click Save.