Lineage Harvester vs. Edge

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:

• ingest using LiHa from our Tableau Sites
• switch to Edge, for the same Sites
• reconcile that there is no change (Global View / export all characteristics) via asset & asset characteristic line-by-line reconciliation
• Test passed ;-) 

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;

1. Metadata
2. Profiling
3. AI-driven data classification
4. Sampling
5. Technical lineage

... whereas Lineage Harvester only gives you 5 (and 1 although Edge has deeper value here too).

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

• Lineage Harvester makes it harder to collaborate with colleagues because you are using files on a local device. Edge can be configured within Collibra's UI where others can freely access the same Edge Capabilities and Connections.
• Lineage Harvester is more technical than Lineage on Edge because you have to use Terminal/Command + JSON script.
• Edge has settings you can configure within the Collibra platform versus having to remember commands that you reference on Collibra's product documentation.
• Edge is probably easier to synchronize because you can set a schedule through the UI on Collibra versus Lineage Harvester where you would need to do it programmatically.