Release 2025.08

• STRAIGHT_JOIN statements.
• Synonyms when using DBlinks that point to other systems.
• Statements that use the TIMESTAMPDIFF function, correctly interpreting time units (for example SECOND and MICROSECOND) as keywords rather than columns, for the MySQL dialect.

• Correctly resolves parameterized source tables (“$$Src_table_nm”) used in SQL Overrides, thereby restoring the expected technical lineage flow.
• Raises an error if the source configuration is incorrectly formatted, thereby preventing integration failure.
• Accurately processes ScheduleTrigger pipelines, ensuring lineage creation for this specific pipeline type.

• Dataplex Catalog integration now supports asset mappings for columns.
• You can now remove an Aspect from your Dataplex source and re-synchronize the data without issues. The Aspect value is now correctly removed from the asset in Collibra after synchronization.
• You can now establish a GCP connection for Dataplex Catalog integration by using Workload Identity Federation (WIF) without encountering the "Failed to retrieve AWS region" error.

• The “schema” value is now used as the default schema, when it is not explicit.
• The “database” value is now used for database mapping.

• A "ResultUnknown" object without a “value” attribute.
• Dynamic query constructions that use the Power Query M function “Value.NativeQuery”.

• Collibra Data Lineage now retrieves column names from the stage definition to ensure accuracy and prevent incorrect values caused by character casing discrepancies.
• Column look-up for SQL columns is no longer case-sensitive.
• Collibra Data Lineage now correctly handles queries where the “AS” keyword is omitted, automatically inferring and inserting it as needed to ensure accurate query parsing and improved processing.

• Correctly handles WITH statements used in MERGE statements.
• Generates correct lineage for UPDATE statements that have Common Table Expressions (CTEs) as targets.

• AKS 1.33
• AWS Fargate using EKS 1.33
• EKS 1.33
• GKE 1.33
• OpenShift 4.19

• Now correctly harvests stored procedures that do not have parameters.
• No longer harvests irrelevant objects from JavaScript user-defined functions (UDFs).

• SQL queries that take a long time to process no longer result in out-of-memory errors.
• SQL queries with a large number of constant values are now processed more quickly and generate accurate highlights.

• Amazon Elastic Container Registry
• Azure Container Registry
• Google Container Registry

• All supported JDBC data sources
• Apache Airflow (via OpenLineage)
• AWS Glue (via OpenLineage)
• Custom technical lineage
• DataStage
• dbt Core
• Informatica PowerCenter
• OpenLineage
• SSIS

New Edge capabilities, per data source, are required and are now available when you choose to connect via a Cloud Connection. For guidance on how to use the new connection option, go to Create a technical lineage via Edge, select the relevant data source, and then click “Cloud Storage connection”.

• The "COPY INTO TABLE FROM <snowflake_stage>" operation. Lineage shows the flow from the underlying cloud storage to the stage and then to the table.
• The “COPY INTO <snowflake_stage> FROM <table>” operation. Lineage shows the flow from the table to the stage to the underlying cloud storage.

In the technical lineage Browse tab pane, the files are shown in accordance with the following hierarchies:

• For Azure: “AZURE” > Account > Container > Directory > Directory (n levels) > File
• For GCS: “GCS” > Bucket > Directory > Directory (n levels) > File
• For S3: “S3" > Bucket > Directory > Directory (n levels) > File

• Collibra Data Lineage now supports TD_UNPIVOT clauses.
• The FOR column in an UNPIVOT clause is now treated as an output column.

• Supports the Until activity type.
• Separates "Pipeline Runs" and "Pipeline Triggers". Additionally, individual objects are separated based on date, ID, or name.