Snowflake: Supported transformation details

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:

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 <table>` command¹ Streams ²	Queries or query paths that are not executed ³ Sequences, including generating new values Snowflake Scripting ⁴ Snowpark Snowpipes
Note Snowflake logs the `COPY INTO <table>` query only when the table is specified as the source in a FROM clause. For more information, go to Read query notes in the ACCESS_HISTORY view topic in the Snowflake documentation. 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. CollibraData Lineage supports lineage that uses streams as a source and lineage on tables that has streams. CollibraData Lineage does not support lineage on a `CREATE STREAM` statement. Snowflake in SQL-API mode doesn't parse Snowflow Scripting, however, queries that run from Snowflake Scripting that are put in ACCESS_HISTORY still contribute to lineage. If the data sharing consumer moves data from the shared view to a table, CollibraData Lineage does not support lineage from the table. Technical lineage for Snowflake in SQL-API mode supports lineage from batches that drop and replace tables frequently. For details, go to Snowflake SQL-API lineage missing due to frequent table replacement in Collibra Support Portal.

Supported transformations

Unsupported queries and transformations

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

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

Note

Snowflake logs the COPY INTO <table> query only when the table is specified as the source in a FROM clause. For more information, go to Read query notes in the ACCESS_HISTORY view topic in the Snowflake documentation.
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.
CollibraData Lineage supports lineage that uses streams as a source and lineage on tables that has streams. CollibraData Lineage does not support lineage on a CREATE STREAM statement.
Snowflake in SQL-API mode doesn't parse Snowflow Scripting, however, queries that run from Snowflake Scripting that are put in ACCESS_HISTORY still contribute to lineage.
If the data sharing consumer moves data from the shared view to a table, CollibraData Lineage does not support lineage from the table.
Technical lineage for Snowflake in SQL-API mode supports lineage from batches that drop and replace tables frequently. For details, go to Snowflake SQL-API lineage missing due to frequent table replacement in Collibra Support Portal.