What to Expect
Documentation level
At the documentation level, dataedo represents the lineage between Source and Destination.
Objects level
At the level of individual elements, the hevo lineage looks like the following.
Source → Transformation
Dataedo creates a lineage from database to Source object in Hevo, and from Source to Transformation, at this stage lineage is object-oriented.
Dataset (Schema mapper) → ETL Program → Destination
The next part of the lineage starts from Dataset (in Hevo it is Schema mapper object) goes to ETL Program and then to Destination object, this object connects by lineage to the database.
Known limitations
- There is no lineage between Transform and Dataset (Shema 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 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.