Only show release notes of Collibra Platform for Government-certified features

Release 2024.01

Release information

  • Publication dates:
    • Release notes: January 2, 2024
    • Documentation Center: January 2, 2024
  • Release date of Collibra 2024.01.0: January 7, 2024
    • Upgrade non-production environments: January 7, 2024
    • Upgrade production environments: January 28, 2024
    • Release date of Collibra 2024.01.1: On demand only
    • Release date of Collibra 2024.01.2: On demand only
    • Release date of Collibra 2024.01.3: On demand only
  • Release date of Edge 2023.11.1: November 5, 2023
  • Release date of Edge 2023.11.2: November 12, 2023
  • Release date of Edge 2023.11.3: November 19, 2023
  • Release date of Edge 2023.11.4: November 26, 2023
  • Release date of Edge 2023.11.5: December 3, 2023
  • Release date of Edge 2023.11.6: December 10, 2023
  • Release date of Edge 2023.11.7: December 17, 2023
  • Release date of Edge 2023.11.8: January 7, 2024
  • Release date of Edge 2023.11.9: January 14, 2024
  • Release date of Edge 2023.11.10: January 21, 2024
  • Release date of Edge 2023.11.11: January 28, 2024
  • Relevant Jobserver version: 2024.01.0-81

Enhancements

Collibra Console

  • We improved the performance of the sign-in process for Collibra Console.

Fixes

Data Catalog

  • The Catalog home page, the Table asset page, and the Data Set asset page now all load faster. (ticket #116267, 124702, 128372)

Data Lineage and BI integrations

  • When Collibra is processing a batch of Looker metadata, an HTTP 400 error indicates a "bad request" with regard to a dashboard. The Collibra Data Lineage service instance now skips such dashboards and resumes processing the rest of the batch. HTTP 400 errors result in an MSG-LIN-8001 error in the lineage harvester logs. The MSG-LIN-8001 error message mentions the problem dashboard ID and the error message from Looker, which might include suggestions for resolving the error.
  • Implemented streaming by the lineage harvester when synchronizing Looker, to help reduce the chances of Out Of Memory (OOM) errors. (ticket # 126225, 128131)
  • When integrating Looker, the lineage harvester now includes a retry mechanism, to reduce the chances of experiencing a GOAWAY error when trying to connect to Looker. (ticket #128131)
  • When integrating Power BI or Azure Data Factory, if the root certificate of the server is not trusted, the issue is now accurately described in the lineage harvester log file. Previously, the issue was inaccurately described as a timeout error.
  • The lineage harvester version 2024.01 now uses Transport Layer Security v1.3 encryption, for heightened security.
  • Optimised memory profile when harvesting database models during the integrating of JDBC data sources. This helps reduce the chances of Out Of Memory (OOM) errors. To accommodate this enhancement, we had to updated some of the SQL queries used for harvesting SAP HANA and Oracle data sources. Please review any customized queries you use that may have been affected by this change. (ticket #130766)

Data Governance

  • A slow running script no longer causes a not-null constraint error when importing code values. (ticket #129698)
  • Checking view permissions for a large number of domains when viewing the relations of an asset no longer causes a data fetching exception. (ticket #127228)

  • We have increased the event system performance for replacing relations in an asset table to decrease a longer wait time.

  • We have fixed an issue of the Dashboard icon displaying as a Warning icon when selecting an icon for an asset type, in some customer preview instances.

  • We have fixed a regression that made it impossible to migrate views between environments. (ticket #129440, 129624, 129822, 129903, 129937, 129962, 130065, 130162, 130166, 130209, 130303, 130541, 130561, 131312)

  • System complex relation types had a system protection that was too strict when the co-role value was different from our out-of-the-box types. This prevented CMA file imports that were downloaded from marketplace.collibra.com. We have fixed this issue.

  • We have fixed an issue of a Complex Relation Type dropdown loading slowly in the import UI. (ticket #126836)

Diagrams

  • When editing the edge properties, the Relation Type drop-down list now shows the relation types that match the value you enter in the corresponding field. (idea #DCC-I-1777)

Workflows

  • Adding proposed values to a Collibra data entry drop-down field in a workflow form no longer prevents searching in that filed. (ticket #122659, 123369, 126359, 129294, 130393)
  • Collapsed date fields in a workflow form no longer store a formatted timestamp. (ticket #116088)
  • Links with target="_blank" in a text display workflow form no longer open in the same window. (ticket #117678, 122321, 126241)
  • The "View relevant changes" section of a workflow task is now available in the task sidebar. (ticket #120499)
  • The description of a checkbox filed in a workflow form now appears below the checkbox. (ticket #124319)
  • While working on a task, you can again see the task in the workflow diagram. (ticket #128026, 131282)
  • With the new front-end experience enabled, a workflow drop-down form with proposed fixed values now populates the drop-down with those values. (ticket #125801)
  • Workflows that generate a downloadable file no longer download the same file twice. (ticket #127436, 127668)

Workflow Designer

  • You can now see the outcome buttons in the Workflow Designer preview of your form. (ticket #124281)

Collibra Console

  • The error message in Collibra Console for a password reset link that has expired now reflects the cause of the error. (ticket #125401)
  • Signing out of Collibra Console no longer causes an unhandled exception error in some cases. (ticket #113524, 129178)

Miscellaneous

  • We have improved the security of Jobserver.

Featuresin preview

A public preview is an upcoming feature or product that is made available to all customers before it is fully ready for general availability so it can be tested and evaluated early. Learn more

Data Catalog

  • When sorting the out-of-the-box data classes in the Data Classification import wizard, the correct data classes remain selected.

Collibra maintenance updates

Collibra 2024.01.1

  • An invalid session ID issue no longer prevents you from accessing Collibra after the upgrade to version 2024.01.
  • We have fixed an issue where, during antivirus scanning of a new file upload, NIST logging files were taking an excessive amount of time to scan. (ticket #127574)

Collibra 2024.01.2

  • It takes less time to open the Register content page (classic UI) and Register Data Source page (latest UI) to register a data source via Edge.

Collibra 2024.01.3

  • Redeploying a workflow with a sub-process when a user task of the sub-process is still active no longer prevents you from completing the user task. (ticket #134284, 137412)

Data Lineage 2024.01.1

  • Technical lineage for IBM DataStage has improved analysis of INSERT statements that use ORCHESTRATE.
  • Technical lineage for Informatica Intelligent Cloud Services (IICS) now includes lineage from presql and postsql commands.
  • For technical lineage for IICS, a bug is fixed regarding case sensitivity. The technical lineage graph now includes more end-to-end lineage for IICS, and stitching to Catalog assets is more accurate.
  • Technical lineage for Informatica PowerCenter now supports sessions in Folders and Workflows. Previously, when a TaskInstance of a Workflow was set to REUSABLE, Collibra Data Lineage looked for sessions only in the Folder.
  • Technical lineagefor Azure Data Factory can now resolve global parameters into their values. With this enhancement, you won’t experience missing lineage or DEFAULT databases or schemas caused by global parameters.
  • All supported BI tools now benefit from SQL extension v2:
    • The Collibra Data Lineage service instances can now successfully process more SQL queries. This results in a more complete lineage, including nodes that represent queries which previously could not be processed.
    • The source code is more intuitively grouped in the transformations table and includes names (for example, “source code 1”), where previously names were “None”. Queries and their relevant assets are now grouped in a single line. Because of this, the source code processed count in the Done column is reduced and the success rate might differ. The lineage itself is unchanged.
  • When integrating Power BI, the URLs on Power BI Report asset pages are now correctly generated and link to the reports in Power BI. (ticket #133430)
  • Previously, when you create technical lineage for SQL Server Integration Services, disabled executables would not produce lineage and would produce the error: "Unable to find connection". Now, disabled executables do not produce lineage and do not produce an error message.
  • You can now create technical lineage for SAP HANA Cloud by using the lineage harvester and set the new hana-cviews-v2 dialect value in the technical lineage configuration file.

Data Lineage 2024.01.2

  • The integration of Power BI with SQL extension v2 (introduced in Collibra Data Lineage 2024.01.1) no longer results in the duplication in Data Catalog of Power BI Column assets that are measures in Power BI. (ticket #130217, 130974, 133913, 133954, 133964, 134009, 134010)
  • When ingesting Oracle data sources, the Collibra Data Lineage service instances now support the COLLATE clause in CREATE TABLE statements.
  • When ingesting Redshift data sources, the Collibra Data Lineage service instances now support AUTO REFRESH parameter in CREATE VIEW statements.
  • Improved folder filtering for Looker integrations.
    Important The following improvements are applicable when filtering by folder ID.
    • Filtering is now carried out via the API, instead of on the Collibra Data Lineage service instances. This means that the lineage harvester accesses only the specified folders, and sends the metadata to the Collibra Data Lineage service instance for processing and ingestion in Data Catalog. Previously, metadata from all folders was sent to the Collibra Data Lineage service instance, where filtering was then carried out. This enhancement greatly improves Looker integration flexibility, speed, and performance.
    • The log files now include more detailed information about the filter results.

Data Lineage 2024.01.4

  • Improved folder filtering for Looker integrations.
    Important The following improvements are applicable when filtering by folder ID.
    • Filtering is now carried out via the API, instead of on the Collibra Data Lineage service instances. This means that the lineage harvester accesses only the specified folders, and sends the metadata to the Collibra Data Lineage service instance for processing and ingestion in Data Catalog. Previously, metadata from all folders was sent to the Collibra Data Lineage service instance, where filtering was then carried out. This enhancement greatly improves Looker integration flexibility, speed, and performance.
    • The log files now include more detailed information about the filter results.
  • When ingesting Snowflake data sources, the Collibra Data Lineage service instances now support multiple SELECT TABLE.* EXCLUDE statements.
  • Fixed an issue that was causing Collibra Data Lineage with SQL extension V2 to show incomplete lineage when system names were used. (ticket #134449)
  • Fixed an issue that was resulting in a "result of string concatenation is too long" error, when ingesting Oracle data sources. (ticket #134226, 134613)
  • Technical lineage for Informatica PowerCenter now includes lineage from pre-session SQL and post-session SQL commands.

Edge and Data Lineage updates

These updates contain security and bug fixes for Data Lineage, Edge sites and their capabilities. These releases may be planned outside the regular monthly or quarterly release. You'll see the fix versions if you are manually upgrading an Edge site or reviewing logs.

Edge 2023.11.1

  • We have improved security for Data Classification via Edge.
  • To improve profiling performance of the profiling capability on Edge, we no longer perform a dedicated query for a row count when you profile all rows in a table. (ticket #121338)
  • The Databricks Unity Catalog Synchronization capability has been updated to use a generated external ID for assets based on the full name. Previously, the external ID was set to the asset Databricks ID.
    This change was made to accommodate the use case where an asset, for example a table, was deleted and recreated with the same name in Databricks Unity Catalog. This resulted in multiple Databricks IDs for the same asset which caused the integration to fail.
    (ticket #126352, 126606, 126608, 127194, 128382)

    Important If you re-synchronize integrated data sources with the new version of the Databricks Unity Catalog Synchronization capability, you will get the following error message: A mapping for the external system id '{your-system-asset-id}' and resource '{resource-id}' already exists. To resolve this, follow the instructions in the knowledge article.

Edge 2023.11.2

  • We have improved the security of Edge.

Edge 2023.11.3

  • If you run the migrate option for the Databricks Unity Catalog Synchronization capability to use a generated external ID, the complex relations mappings are now removed as well. For information on the migration option, go to https://support.collibra.com/hc/en-us/articles/18702127233815
  • We have improved the security of Data Quality & Observability Classic.

Edge 2023.11.4

  • We have improved the security of Data Quality & Observability Classic

Edge 2023.11.5

  • We have improved the security of Data Lineage.
  • We have improved the security of Data Classification.
  • We have improved the security of S3 synchronization.

Edge 2023.11.6

  • We have improved the security of Data Classification.
  • We have improved the security of Catalog JDBC ingestion and JDBC Profiling.
  • When creating technical lineage via Edge, you can now use a man-in-the-middle (MITM) proxy between Edge and the Collibra Data Lineage service instances. For details on which data sources support the use of proxies, see Create a technical lineage via Edge and select your data source. (ticket #120946, 121788, 124013, 124390, 126170, 128684, 130493)

Edge 2023.11.7

  • We have improved the security of Data Classification, Data Lineage, ADLS synchronization, and Databricks Unity Catalog synchronization.

Edge 2023.11.8

  • We have improved the security of Collibra Protect, Catalog JDBC ingestion, and JDBC Profiling.
  • The GCS integration now also stores the bucket location in the Location attribute of the GCS bucket asset.
  • The ADLS-Purview integration now supports the integration of more than 120 columns from Purview. (ticket #130324)

Edge 2023.11.9

  • We have improved the security of ADLS synchronization, Collibra Protect, Databricks Unity Catalog synchronization, GCS synchronization and S3 synchronization.

Edge 2023.11.10

  • We have improved the security of Data Classification.

Edge 2023.11.11

  • When integrating Tableau, if a password is not provided for the Tableau connection, the integration fails, as expected. The error message now correctly identifies the issue. (ticket #130856)
  • Fixed an issue that was resulting in a "result of string concatenation is too long" error, when ingesting Oracle data sources. (ticket #134226, 134613)
  • Optimized memory profile when harvesting database models during the integrating of JDBC data sources. This helps reduce the chances of Out Of Memory (OOM) errors. (ticket #130766)
  • When you create technical lineage for Matillion, technical lineage via Edge now supports passing a certificate to the data source for authentication.
  • Collibra Data Lineage now supports lineage from SAP HANA calculated views in SAP HANA Cloud and Advanced data sources.
  • Previously, Collibra used dbt Labs' Discovery API job schema, which gets information from the applied state based on the most successful job runs. This method had 2 issues:
    • It depended on access to the Admin API, which not all dbt Cloud customers had.
    • It does not include all jobs compile projects or produce models, for example, a macro command.
    Now, Collibra uses the environment schema, which is available to all dbt Cloud customers, and can get design lineage by pulling definition state. For more information, go to project state in dbt docs.