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

Release 2023.10

Release information

  • Publication dates:
    • Release notes: October 5, 2023
    • Documentation Center: October 5, 2023
  • Release date of Collibra 2023.10.0: October 8, 2023
    • Upgrade non-production environments: October 8, 2023
    • Upgrade production environments: October 29, 2023
  • Release date of Collibra 2023.10.1: 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

Highlights

  • Data Catalog
  • Following a Snowflake communication, all Snowflake instances deployed on GCS must use JDBC driver 3.13.25 or newer by November 1, 2023.
    Make sure to update your driver in the Edge connection or Jobserver configuration before November 1, 2023.
    Go to Collibra Marketplace to find the latest driver.

Enhancements

Protect

  • The Protectdocumentation now contains videos that show how to set up Protect for a BigQuery data source.

Collibra Console

  • The "Enhanced CSRF" Console configuration option is now enabled by default to validate REST requests using a Spring Security CSRF token.

Security

  • We have improved the Collibra platform protection against CSRF (Cross-Site Request Forgery) attacks. Also, all inline scripts are blocked by a new, more restrictive CSP (Content Security Policy). These security improvements will be applied to all new environments from now on. The enhancements will be rolled out to existing environments throughout 2024.

Fixes

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

  • When creating a technical lineage via the lineage harvester, with a proxy, the proxy configuration is again correctly logged only after the initial connection by the lineage harvester to the proxy. (ticket #124387)
  • Collibra Data Lineage can now handle asset names that include characters other than alphabetical letters and numeric digits. Previously, if an asset name contained non-alphanumeric characters, the technical lineage viewer failed to display the technical lineage and returned an internal server error. (ticket #123618)
  • Collibra Data Lineage supports multiple schemas in linear taskflows (workflows) in Informatica Intelligent Cloud Services.
  • When you create technical lineage for DataStage, and the final stage of a job is Reject, the lineage is now parsed appropriately.

Collibra DQ

  • An authentication issue no longer prevents Collibra Data Quality & Observability from connecting to Collibra. (ticket #125495)

Data Governance

  • You can again see the number of removed resources in the activities list summary as a result of refreshing a schema of a registered data source via Jobserver. (ticket #108374)

Search

  • Search results no longer show hexadecimal codes in place of special characters. (ticket #124571, 124809, 125354, 125590)

Collibra Console

  • You can now see correct user IP addresses in the NIST audit logs. (ticket #117078)

Miscellaneous

  • Scheduled backup names no longer contain unsupported characters. (ticket #124000)
  • New users that do not have a role with the System Administration global permission are no longer subscribed by default to scheduled maintenance notifications.
  • Inactive Collibra features no longer cause an unusual amount of irrelevant errors in the log files. (ticket #120922, 124899, 124928, 124974, 125195, 125315, 125512, 125654, 126362, 126429, 126661)

Collibra maintenance updates

Collibra 2023.10.1

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

Data Lineage 2023.10.2

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

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 Beta 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 (Beta) 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)