Auto Lineage Prerequisites

There are certain prerequisites that need to be completed while creating a connection before building the lineage automatically.

In Administration > Connectors, adding a connector involves entering connector details and license add-on options. Only the Connector Creator can select the Auto Lineage option to build lineage automatically. This option enables tracking data origins (source and destination) and paths. Provide all connection details, save, and validate to ensure the correct setup.

Crawler Settings

Users can select a validated connector, click the Nine Dots menu, and select the settings option. Then, select the crawler option on the top pane and follow the options as per the required connector.

For example, the setup of an RDBMS connector differs from that of a report connector. Users with the Integration Admin role can configure these settings.

RDBMS Connector

RDBMS connectors have a more specific process for setting up auto lineage creation.

We can perform Crawl on Procedures, Functions, Triggers, and Views Source Codes:

• Save the connection and validate.

• Click on the Nine Dots menu on the connector page.

• Within the settings, go to the crawler option at the top pane and enable the checkbox for "Tables, Views, & columns,” “Procedures, Functions, Triggers, and Views Source Codes,” and “Relationship."

These codes are essential for creating a detailed data lineage that accurately represents the source system. They are the building blocks for creating lineage, providing a complete view of the data flow.

Reporting Connectors

Reporting connectors follow these steps to enable the auto lineage-building feature. Here's a detailed explanation.

Crawling Report Columns:

Select the “Reports” and "Report Columns" checkboxes in the crawler settings and crawl these specific report columns from the source system.

The Lineage tab in the crawler settings allows users to change the server/source connection to build lineage. This feature enables the selection of multiple servers at once to build lineage from required tables.

Select server dialects to use for parsing source code:

The selected dialects will parse source codes in order. If the first dialect can't parse the code, it will try the next ones until it is successful. If all fails, lineage won't build, showing a parse failure. Specify at least one dialect for building lineage for the connector codes.

Connector priority to specify the connection for the table Lineage: If a table with the same name appears in multiple connector cataloged tables, the user must set the connector priority to choose which table to use for lineage building.

For example, if both SQL Server and PostgreSQL have a customer table, and PostgreSQL is set before SQL Server, the lineage will come from the PostgreSQL customer table.

ETL Connector

ETL connectors require specific steps to enable the auto lineage-building feature. They have the same Lineage tab options as Reporting connectors.

---

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.