Skip to main content

Hevo–Automatic Data Lineage

What to Expect​

Documentation Level​

At the documentation level, Dataedo represents the lineage between Source and Destination.

Image title

Objects Level​

At the level of individual elements, the Hevo lineage looks like the following.

Source → Transformation​

Dataedo creates a lineage from the database to the Source object in Hevo, and from Source to Transformation. At this stage, the lineage is object-oriented.

Image title

Dataset (Schema Mapper) → ETL Program → Destination​

The next part of the lineage starts from the Dataset (in Hevo, it is the Schema Mapper object), goes to the ETL Program, and then to the Destination object. This object connects by lineage to the database.

Image title

Known Limitations​

  • There is no lineage between Transform and Dataset (Schema Mapper) because we do not parse these scripts.
  • Sources or destinations that are not supported by Dataedo will not have data lineage.
  • Dataedo only imports information from the source connectors that are currently connected.

Troubleshooting​

No Data Lineage After the First Import​

Follow the steps starting from the Assigning Linked Sources section in the Connecting to Hevo article.

No Object-Level Data Lineage​

Make sure that the source and destination are assigned to the corresponding Linked Source in Dataedo. If they are assigned, try re-importing changes. You can find more information in the Connecting to Hevo article under the Assigning Linked Sources and Importing Changes for Data Lineage sections.

On this page
Dataedo LogoDataedo Logo
If you have any questions or need assistance, feel free to reach out to the Dataedo support team.
Dataedo support