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

Release 2023.09

Release information

  • Publication dates:
    • Release notes: September 7, 2023
    • Documentation Center: September 7, 2023
  • Release date of Collibra 2023.09.0: September 10, 2023
    • Upgrade non-production environments: September 10, 2023
    • Upgrade production environments: October 1, 2023
  • Release date of Collibra 2023.09.1: October 1, 2023
  • Release date of Collibra 2023.09.2: October 15, 2023
  • Release date of Edge 2023.08.1: August 20, 2023
  • Release date of Edge 2023.08.2: September 10, 2023
  • Release date of Edge 2023.08.3: October 1, 2023
  • Release date of Edge 2023.08.4: October 8, 2023
  • Release date of Edge 2023.08.5: October 15, 2023
  • Release date of Edge 2023.08.6: October 22, 2023
  • Release date of Edge 2023.08.7: October 29, 2023
  • Release date of Edge 2023.08.8: November 5, 2023
  • Relevant Jobserver version: 2023.08.2-51

New features

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

  • Technical lineage for dbt Cloud and Core is now in preview. For dbt Cloud, you can create technical lineage on Edge or by using the lineage harvester. For dbt Core, you can create technical lineage by using the lineage harvester only.

Enhancements

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

  • Collibra Data Lineage now supports the Power Query M function Teradata.Database.
  • The MicroStrategy integration now supports MicroStrategy Freeform SQL. To benefit from this enhancement, you need MicroStrategy version 10 or newer, or MicroStrategy ONE.
  • Several changes to Snowflake SQL-API mode lineage harvester queries were made. If you use technical lineage via Edge, update the Access History, Objects Modified, and Columns Joined queries. For more information, go to Create a technical lineage via Edge for Snowflake.

    A new schemaNames property is added, so you can now use an inclusive filter to specify which schemas to harvest lineage from. In addition, duplicate information in the results was removed, producing smaller result files and faster query times.

Security

  • The sign in dialog box now blurs the contents of the page you were on after an expired session.

Fixes

Data Catalog

  • Database assets that have a relation with more than one System asset, no longer cause the 'No data available' message on the Register Content page. The validation to make sure only one System asset is linked to a Database asset is now performed only during the synchronization of the database. (ticket #96851, 99742, 103906, 111486, 116103, 119881)
  • Users with restricted View permissions on any already registered Database asset no longer get the 'No data available' message on the Register Content page. Instead they can now see the databases to which they have View permission and register new data sources with Edge. (ticket #115800, 117914)
  • Oracle does not apply the optional table-profiling-queries-timeout property in the profiling capability. To make sure that a profiling query timeout is applied for an Oracle data source, add the oracle.jdbc.ReadTimeout property in milliseconds to the Edge connection. (ticket #119731, 121808)

  • When registering a data source via Edge, instead of endlessly starting "database list" jobs in case of an error, we now properly report the error on the initial job.

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

  • When integrating Tableau, the import job no longer fails if an ingested calculation rule exceeds the size limit of 100,000 bytes, which is approximately 100,000 characters in length. (ticket #120086)
  • When integrating MicroStrategy, Metric Attributes are now identified in the technical lineage and in Data Catalog by their names, instead of an asterisk (*), and their source type is now “Metric Attribute”. (ticket #121495)

Data Governance

  • You can again see the name of the file you used during an import in the activities list. (ticket #119324, 120266)
  • Importing large Excel files no longer prevents the import to complete. (ticket #122693)

Data Marketplace

  • When attributes are deleted from an asset type global assignment, they are now correctly removed from the Data Marketplace asset preview. (ticket #117542 )

Workflow Designer

  • Clearing a data entry or selection field in a workflow form that was designed using the Workflow Designer no longer causes the variable to retain the previous value and now returns null. (ticket #110284, 111443, 115554, 118431, 119603, 119605, 122447, 122448)

Security

  • Signing in after an expired session no longer redirects you away from the page you were viewing. (Idea #PE-I-1651)

API

  • You can again remove domains using the REST Core API v2 POST method of the /domains/removalJobs endpoint. (ticket #119964)
  • Sorting by attribute using the REST Core API v2 Output Module endpoints no longer causes an error response code. (ticket #118367)
  • The results of a Knowledge Graph API query for user and user group read permissions for domains or communities now contain both user and user group details where applicable.

Miscellaneous

  • When you add a relation to an asset in a hierarchy view, the relation is now shown instantly and you no longer need to refresh the page. (ticket #119406, 120238)

Collibra maintenance updates

Collibra 2023.09.1

  • Data Catalog views with hierarchies no longer take an unusual amount of time to load. (ticket #116828, 117222)
  • We have improved the security of our authentication, authorization, cryptography, and session management.
  • A session time out no longer causes the Workflow Designer to become inaccessible. (ticket #123795, 123798, 123800, 123926, 124097, 124155, 124216, 124380, 124391, 124488, 124527, 124671)
  • An authentication issue no longer prevents Data Quality & Observability Classic from connecting to Collibra. (ticket #125495)

Collibra 2023.09.2

  • Programmatic user accounts can again function uninterruptedly when a password expiration interval exists.

Data Lineage 2023.09.12

  • You can now configure a proxy connection when integrating Power BI via the lineage harvester.

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.08.1

  • We have improved one or more private preview features.

Edge 2023.08.2

  • EKS 1.22 is no longer supported for new Edge installations starting from the 2023.09 release. If you plan to install a new Edge site on 2023.09 or later, you must use an EKS cluster with Kubernetes version 1.23 or higher.
  • We have improved the security of Edge.
  • When integrating with Databricks Unity Catalog, in Column assets that have a structured technical data type, Array or Struct, you can now click the “More” button to see the structure of the data.

Edge 2023.08.3

  • The technical lineage for dbt Cloud (in preview) on Edge is using a new API to get information, as the previous API used is deprecated.

Edge 2023.08.4

  • We have improved the security of Edge.
  • You can now configure a proxy connection when integrating Power BI.
  • The Edge Classification capability has been updated to handle empty spaces around data. (ticket #114742)
  • Advanced configuration options are now available for the following integration capabilities: S3, GCS, ADLS, and Databricks Unity Catalog. The advanced configuration, Memory (MiB), Logging configuration, and JVM arguments, can help when investigating issues and should only be completed on request of or together with Collibra Support.
  • It is now possible to use the GCS synchronization with MITM proxy with basic authentication.
  • If the current S3 synchronization crawler configuration doesn’t meet your needs, we now provide a way to integrate an AWS Glue database for which you defined crawlers in AWS Glue itself. This allows you to use all crawler options from the AWS Glue Console.
    The new “Glue database configuration” parameter is available in the S3 Synchronization capability. There, you can enter the Glue database name, region, and Collibra domain ID in which you want to add the assets, in JSON format.

    Note If you use the "Glue database configuration" parameter, you will still need to create a dummy crawler in DIC. This dummy crawler configuration will be ignored by the S3 synchronization. In a future release, we'll improve the process and remove the need for a dummy crawler.

  • The Databricks Unity Catalog integration now integrates both the Primary key and Foreign key information from Databricks Unity Catalog.

Edge 2023.08.5

  • Fixed several harvester issues that were causing Power BI integration to fail. (ticket #124899, 125669, 126040, 127166, 127350, 127384, 127409)

Edge 2023.08.6

  • 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)

Edge 2023.08.7

  • We have improved security for Data Classification via Edge.

Edge 2023.08.8

  • 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)