Change log lineage harvester archive

Since lineage harvester 1.2.0, the lineage harvester is a part of the Collibra Data Intelligence Cloud release.

Tip Collibra Data Lineage supports a limited list of data sources. For the most recent list, check the supported data sources topic in the Technical lineage section of the documentation.

Versions

Collibra Data Intelligence Cloud version	Lineage harvester version
2021.10	1.4.3
2021.09	1.4.2
2021.07	1.4.1
2021.06	1.4.0
2021.05	1.3.6 1.3.5
2021.04	1.3.4
2021.03	1.3.3
N/A	1.3.2
2021.01	1.3.1
2020.12	1.3.0
2020.11	1.2.1
2020.10	1.2.0
2020.09	1.1.7

Important We highly recommend to download and use the newest lineage harvester from the Collibra downloads page, even if you have an older version of Collibra Data Intelligence Cloud.

1.4.2

See the 2021.09 release notes.

1.4.1

See the 2021.07 release notes.

1.4.0

See the 2021.06 release notes.

1.3.6

The lineage harvester now works correctly when you create a technical lineage for Amazon Redshift, Azure SQL server, Greenplum, HiveQL, SAP Hana and Spark SQL. (ticket #65586)

1.3.5

See the 2021.05 release notes.

1.3.4

See the 2021.04 release notes.

1.3.3

See the 2021.03 release notes.

1.3.2

See the 2021.03 release notes.

1.3.1

See the 2021.01 release notes.

1.3.0

See the 2020.12 release notes.

1.2.1

See the 2020.11 release notes.

1.2.0

See the 2020.10 release notes.

What's new in older versions

1.1.7

See the 2020.09 release notes.

1.1.6

When you run the full-sync command in the lineage harvester, you now know immediately whether or not the connection to the Technical lineage server is successful.

1.1.5

Feature "Break lineage" or features "Break inbound" and "Break outbound", depending on the data object, are no longer available.
You can now create a technical lineage for SAP HANA calculation views.

1.1.4

You can now create a technical lineage without stitching the data objects in your technical lineage to Table and Column assets in Data Catalog.

1.1.3

You can now create a technical lineage for data sources in Informatica PowerCenter.

1.1.2

Analysis of SQL source codes is now only available on the Status page of your technical lineage.

1.1.1

You can now create a technical lineage for IBM DB2 data sources.
You can now create a technical lineage for SAP Hana data sources.
You now have a status page on which you can see the log files of the analysis of the SQL source codes.
In the Browse tab pane, you can no longer select a schema. You can still select a table or column.

1.1.0

You can now connect to an Oracle database that uses a service name instead of an SID.
You can now create a technical lineage for data sources that were previously uploaded to the lineage harvester.
You can now edit a Google BigQuery SQL file to exclude specific data sets from your technical lineage.

Fixes

1.1.7

See 2020.09 release notes.

1.1.6

The lineage harvester now correctly shows the cause of an exception.

1.1.5

Relations of the type "Data Element targets / sources Data Element" are now created correctly.

1.1.4

The zoom functionality now works correctly.
The lineage harvester is now more resilient if short server outages are encountered.

1.1.3

The term "sqldep" is now replaced by "techlin" in the lineage harvester and configuration file.
The descriptions of the command options and arguments in the lineage harvester are improved.
The command /bin/lineage-harvester --help now correctly shows a help message.
The extractQueries field is now removed from the configuration file.

1.1.2

Error message Technical lineage cannot be shown is now improved.
The lineage harvester no longer returns an error when you run a job on Windows.

1.1.1

The lineage harvester no longer uploads data sources without SQL files to the Collibra lineage.
The lineage harvester now successfully uploads Amazon Redshift materialized views.
The technical lineage now shows Expired Techlin API key when your API key is expired.

1.1.0

The Technical lineage tab page is now improved.
The lineage harvester now shows error code UserKeyExpired when your API key is expired.
The technical lineage now shows Expired Techlin API key one year after your API key is expired.