Relationships created for technical lineage
we are in the process of building the technical lineage for our assets (Tables and columns), we don’t have the license for lineage harvester feature rather we use different application for our lineage use case.
To build the integrated view we are planning to ingest brief lineage into Collibra.
Q) May i know what is the relations I should be creating for lineage for table to table and column to column.
Q) If in-case we don’t the relation already existing, can we create the relations with the same name or do we need to create with specific details such as UUID.
Q) Hope we don’t need to additional license to visualize the lineage harvested else where and ingested into Collibra.
Appreciate any comments on this topic.
manjunathnarayanawamy
Posted 3 years ago · Edited 1 year ago·Last reply 1 year ago
1 comment
adamstanczak
·1 year ago · EditedHi @manjunathnarayanawamy,
Simple answer for Q1 is Data element source/target Data element (build-in). This relation is used for stitching when applying relations tech lineage discovered.
Now, if you plan to manually create relations between assets, you can use any relation type you want, just bring it properly to diagram and you can visualize your assets map. No need to use lineage relation. This will not be visible in tech lineage browser anyway, only diagrams.
Adam