Supported transformation details

Collibra Data Lineage supports the most commonly used transformations in the following sources:

Azure Data Factory
dbt Cloud (Beta)
IBM DataStage
Informatica PowerCenter
Informatica Intelligent Cloud Services
Snowflake
SQL Server Integration Services

Azure Data Factory

Collibra Data Lineage supports the most commonly used transformations and data sources in Azure Data Factory.

Supported transformations

The following tables shows a non-exhaustive list of supported and unsupported transformations.

Supported transformations	Unsupported transformations
Aggregate¹ Alter Row Assert Derived Column¹ Exists External Call² Filter Flatten¹ Join Lookup Parse¹ Pivot³ Rank Select¹ Sink⁴ Sort Source Split Stringify Surrogate Key Union Unpivot Window¹	Some reserved variables names, for example {@context} Flowlets
Limitations Transformations that contain column patterns or rule-based mappings can only be partially analyzed because they generate column names on the fly during the actual data flow run. If technical lineage is detected from a dynamically generated column, it is given the placeholder Dynamic Column in the technical lineage viewer. In the Mapping section of the editor, column patterns are not supported and not displayed in the technical lineage graph. Note that Auto mapping uses column patterns behind the scenes and is therefore not supported either. Pivoted columns can only be inferred when explicit values are provided in the Pivot Key tab. When columns cannot be inferred, a placeholder Pivoted Columns is added. The SQL scripts and rule-based mappings in the transformation are not supported.

Supported transformations

Unsupported transformations

Aggregate¹
Alter Row
Assert
Derived Column¹
Exists
External Call²
Filter
Flatten¹
Join
Lookup
Parse¹
Pivot³
Rank
Select¹
Sink⁴
Sort
Source
Split
Stringify
Surrogate Key
Union
Unpivot
Window¹

Some reserved variables names, for example {@context}
Flowlets

Limitations

Transformations that contain column patterns or rule-based mappings can only be partially analyzed because they generate column names on the fly during the actual data flow run. If technical lineage is detected from a dynamically generated column, it is given the placeholder Dynamic Column in the technical lineage viewer.
In the Mapping section of the editor, column patterns are not supported and not displayed in the technical lineage graph. Note that Auto mapping uses column patterns behind the scenes and is therefore not supported either.
Pivoted columns can only be inferred when explicit values are provided in the Pivot Key tab. When columns cannot be inferred, a placeholder Pivoted Columns is added.
The SQL scripts and rule-based mappings in the transformation are not supported.

Supported data sources

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.

Data sources	Dataset type	Linked service type
Amazon Redshift	AmazonRedshiftTable	AmazonRedshift
Azure Blob storage	AzureBlob	AzureBlobStorage
Azure Data Lake Storage Gen2	AzureBlobFSFile	AzureBlobFS
Azure Data Lake Store	AzureDataLakeStoreFile	AzureDataLakeStore
Azure Databricks Delta Lake	AzureDatabricksDeltaLake	AzureDatabricksDeltaLake
Azure SQL Managed Instance	AzureSqlMITable	AzureSqlMI
Azure SQL Server database	AzureSqlTable	AzureSqlDatabase
Azure Synapse Analytics	AzureSqlDWTable	AzureSqlDW
DB2 data source	Db2Table	Db2
Google Cloud Storage	GoogleCloudStorageLocation	GoogleCloudStorage
Microsoft Access	MicrosoftAccessTable	MicrosoftAccess
Microsoft Azure Cosmos Database	CosmosDbSqlApiCollection	CosmosDb
Open Database Connectivity (ODBC)	OdbcTable	Odbc
On-premises Oracle database	OracleTable	Oracle
REST	RestResource	RestService
Salesforce	SalesforceObject	Salesforce
Salesforce Marketing Cloud	SalesforceMarketingCloudObject	SalesforceMarketingCloud
Salesforce Service Cloud	SalesforceServiceCloudObject	SalesforceServiceCloud
SAP Business Warehouse (open hub)	SapOpenHubTable	SapBW
SFTP server	SftpLocation	Sftp
Snowflake	SnowflakeTable	Snowflake
SQL Server	SqlServerTable	SqlServer

dbt Cloud (Beta)

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 materializedMapping property in the <source ID> configuration file.
If you use the lineage harvester, specify the materializedMapping property in the Source Configuration field in the Technical Lineage for dbt Cloud capability.

IBM DataStage

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.

Informatica PowerCenter transformations

The following table shows a non-exhaustive list of supported and unsupported transformations in Informatica PowerCenter.

Supported transformations	Unsupported transformations
Aggregator Expression¹ Filter Input Joiner Lookup Mapplet Normalizer Output Rank Router Sorter Source SQL in the `translate_db_type` function Target Transaction Control Union Update Strategy	Data Masking Java Sequence Generator Stored Procedure² Web Services XML
Note The transformation is shown if the column (expression) is using at least one column from another connected transformation. The stored procedures are stored and run in the databases that Informatica PowerCenter connects to. Collibra Data Lineage does not access the Informatica PowerCenter data sources, so Collibra Data Lineage collects the stored procedure names but does not support the Stored Procedure transformation.

Supported transformations

Unsupported transformations

Aggregator
Expression¹
Filter
Input
Joiner
Lookup
Mapplet
Normalizer
Output
Rank
Router
Sorter
Source
SQL in the translate_db_type function
Target
Transaction Control
Union
Update Strategy

Data Masking
Java
Sequence Generator
Stored Procedure²
Web Services
XML

Note

The transformation is shown if the column (expression) is using at least one column from another connected transformation.
The stored procedures are stored and run in the databases that Informatica PowerCenter connects to. Collibra Data Lineage does not access the Informatica PowerCenter data sources, so Collibra Data Lineage collects the stored procedure names but does not support the Stored Procedure transformation.

Informatica Intelligent Cloud Services

The following table shows a non-exhausitive list of supported taskflows and unsupported tasks in Informatica Intelligent Cloud Services.

Supported taskflows	Unsupported tasks
Taskflow Linear Taskflow	Parallel tasks Parallel tasks with decision Sequential tasks Sequential tasks with decision Single task

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.

Supported transformations	Unsupported transformations, functions and constructions
Data-driven conditions Expression, including custom expressions in the supported transformations Filter Joiner, including join conditions Lookup Mapplet Router Sequence Generator Source Stored Procedure Target Union	Aggregator Cleanse Data Masking Deduplicate Hierarchy Builder Hierarchy Parser Hierarchy Processor Input Java Labeler Machine Learning Normalizer NEXTVAL Parse Python Rank Rule Specification Structure Parser Transaction Control Velocity Verifier Web Services

Snowflake

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
Snowpark

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.

Supported transformations	Unsupported queries and transformations
Using a driver Data Definition Language (DDL) queries Direct login Stored procedures The `COPY INTO` DML command Streams ²	Queries or query paths that are not executed ¹ Sequences, including generating new values Snowflake Scripting Snowpark Snowpipes
Note If you create technical lineage for Snowflake by using the JDBC connection type, only queries or query paths that are executed are supported. For example, if a SQL query contains a CASE statement, the technical lineage will only show lineage from the WHEN path that was executed. However, if you use the folder connection type to ingest Snowflake, SQL queries that include all paths of a CASE statement will be parsed and reflected in the technical lineage. Collibra Data Lineage supports lineage that uses streams as a source and lineage on tables that has streams. Collibra Data Lineage does not support lineage on a `CREATE STREAM` statement.

Supported transformations

Unsupported queries and transformations

Using a driver
Data Definition Language (DDL) queries
Direct login
Stored procedures
The COPY INTO DML command
Streams ²

Queries or query paths that are not executed ¹
Sequences, including generating new values
Snowflake Scripting
Snowpark
Snowpipes

Note

If you create technical lineage for Snowflake by using the JDBC connection type, only queries or query paths that are executed are supported. For example, if a SQL query contains a CASE statement, the technical lineage will only show lineage from the WHEN path that was executed. However, if you use the folder connection type to ingest Snowflake, SQL queries that include all paths of a CASE statement will be parsed and reflected in the technical lineage.
Collibra Data Lineage supports lineage that uses streams as a source and lineage on tables that has streams. Collibra Data Lineage does not support lineage on a CREATE STREAM statement.

SQL Server Integration Services (SSIS)

Collibra Data Lineage supports the following non-exhaustive list of transformations and component types in SQL Server Integration Services:

Supported transformations	Supported component types
Aggregate Cache Transform Conditional Split Data Conversion Derived Column Fuzzy Grouping Lookup Merge Join Multicast OLE DB Command Row Count Script Component Slowly Changing Dimension Sort Union All	Microsoft.ADONETDestination Microsoft.DataReaderSourceAdapter Microsoft.XmlSourceAdapter Microsoft.ScriptComponentHost

Supported transformations

Supported component types

Aggregate
Cache Transform
Conditional Split
Data Conversion
Derived Column
Fuzzy Grouping
Lookup
Merge Join
Multicast
OLE DB Command
Row Count
Script Component
Slowly Changing Dimension
Sort
Union All

Microsoft.ADONETDestination
Microsoft.DataReaderSourceAdapter
Microsoft.XmlSourceAdapter
Microsoft.ScriptComponentHost

Important

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.