Collibra Data Lineage supports the most commonly used transformations in the following sources:
- Azure Data Factory
- Databricks Unity Catalog (Beta)
- dbt Cloud
- IBM DataStage
- Informatica PowerCenter
- Informatica Intelligent Cloud Services
- SQL Server Integration Services
The following tables shows a non-exhaustive list of supported and unsupported transformations.
The following table shows a non-exhaustive list of supported sources with the corresponding dataset and linked service types.
CollibraData Lineage supports all data format types that are supported in Azure Data Factory, including binary, Excel file, Delimited text, JSON, Parquet, and so on.
|Linked service type
|Azure Blob storage
|Azure Data Lake Storage Gen2
|Azure Data Lake Store
|Azure Databricks Delta Lake
|Azure SQL Managed Instance
|Azure SQL Server database
|Azure Synapse Analytics
|DB2 data source
|Google Cloud Storage
|Microsoft Azure Cosmos Database
|Open Database Connectivity (ODBC)
|On-premises Oracle database
|Salesforce Marketing Cloud
|Salesforce Service Cloud
|SAP Business Warehouse (open hub)
Collibra Data Lineage retrieves lineage information from the lineage system tables that build on the Unity Catalog's data lineage feature, and visualizes lineage down to the column level, including notebooks, which are also captured in the lineage system tables.
Collibra Data Lineage retrieves lineage information from the lineage system tables and does not parse the language used to develop notebooks and jobs in Databricks to generate technical lineage. Therefore, you can use any supported language in Databricks. For examples of how Unity Catalog captures and presents data lineage, go to Capture and view data lineage with Unity Catalog in the Databricks documentation.
Note that while Collibra Data Lineage retrieves lineage information from notebooks, Collibra Data Lineage does not ingest or include the notebook assets in the technical lineage.
Collibra Data Lineage supports materialization, and tables and views are treated like tables by default. You can customize the setting in one of the following ways so that the tables and views are treated like views:
- If you use technical lineage via Edge, specify the
materializedMappingproperty in the <source ID> configuration file.
- If you use the lineage harvester, specify the
materializedMappingproperty in the Source Configuration field in the Technical Lineage for dbt Cloud capability.
IBM DataStage uses jobs with stages instead of transformations. IBM Datastage has three job types: parallel jobs, sequence jobs and server jobs. For a list of all job stages per job type in IBM DataStage, read the IBM documentation.
Technical lineage for DataStage supports the following parameters and expressions:
Runtime parameters in parameter set files.To include the runtime parameters, ensure to export DataStage files with executables. For more information, go to Prepare an external directory folder for the lineage harvester if you use the lineage harvester, or Create a technical lineage via Edge for DataStage.
- Expression format. The analysis result displays the DATASTAGE_EXPRESSION message when a complex format with advanced functions is parsed.
The following table shows a non-exhaustive list of supported and unsupported transformations in Informatica PowerCenter.
The following table shows a non-exhausitive list of supported taskflows and unsupported tasks in Informatica Intelligent Cloud Services.
The following table shows a non-exhaustive list of supported and unsupported transformations and constructions in Informatica Intelligent Cloud Services. Specifically, transformations and constructions in the Cloud Data Integration service.
Unsupported transformations, functions and constructions
You can create technical lineage for Snowflake by using SQL Snowflake ingestion mode or SQL-API Snowflake ingestion mode. Collibra Data Lineage supports different queries and transformations for each ingestion method. For more information about the ingestion methods, go to Technical lineage for Snowflake ingestion methods.
SQL Snowflake ingestion mode
With the SQL Snowflake ingestion mode, Collibra Data Lineage does not support the following non-exhaustive list of transformations:
- Snowflake Scripting
SQL-API Snowflake ingestion mode
With the SQL-API Snowflake ingestion mode, Collibra Data Lineage supports the Data Manipulation Language (DML) statements from the following sources. The table also shows a non-exhaustive list of unsupported queries and transformations.
Unsupported queries and transformations
Collibra Data Lineage supports the following non-exhaustive list of transformations and component types in SQL Server Integration Services:
Supported component types
- Collibra Data Lineage supports SQL, but cannot parse other languages or scripts, for example SHELL and BAT scripts.
- SQL statements from Excel are not supported.
- All SQL queries must be preceded by the SELECT or WITH keyword, or else they will be skipped. If a comment precedes the SELECT or WITH keyword, the query will be parsed as expected.
- Collibra Data Lineage does not create lineage for disabled executables.