24 Messages
•
4.8K Points
Lineage Harvester vs. Edge
Hi. I'm new to Collibra. Currently, we're using both Lineage Harvester and Edge for ingesting Technical lineage from various sources.
Can anyone give me an idea what's the advantages and disadvantages of using Lineage Harvester vs Edge?
I would like to know, based on your experience which one is better to use for certain sources such as Power BI, Tableau, SSRS, SSIS, Databricks Unity Catalog?
I found this reference in another thread: Supported data sources for technical lineage (collibra.com) and for some data sources line Tableau and PowerBI, both Lineage Harvester and Edge can be utilized. What's the best practice and considerations in choosing what to use?
Thanks!
grantrollerson1
143 Messages
•
9.8K Points
7 months ago
Lineage Harvester won't be round forever, suggest switching. They are apparently at functional parity. We are moving our Tableau across as soon as Edge gets packaged internally for deploy into Prod. We have though tested in Dev that the migration works.
Runbook, in Dev:
Remember the backstory is Collibra purchased SQLdeb in 2019, which had it's own ingestion method Lineage Harvester. It's taken awhile but they have moved that capability across to Edge now, so the LiHa can fall away, goodbye.
Collibra Announces Acquisition of SQLdep | Collibra
Edge gives you substantially more functionality too;
... whereas Lineage Harvester only gives you 5 (and 1 although Edge has deeper value here too).
(edited)
0
SeanPyle
88 Messages
•
2.8K Points
7 months ago
Hi,
Collibra University has a free course, which may help you understand more about using Edge for Technical Lineage: Why you should use Lineage on Edge today.
My thoughts
(edited)
2
0