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

Release 2023.01

Release information

  • Release date of 2023.01.0: January 8, 2023
    • Upgrade non-production environments: January 8, 2023
    • Upgrade production environments: January 29, 2023
  • Relevant Jobserver version:
    • 2022.11.0-52 (uses PostgreSQL 10)
    • 2023.01.0-63 (uses PostgreSQL 11)

Highlights

  • In Collibra Platform 2023.01, we have upgraded to PostgreSQL 11.17 to ensure that your Collibra can continue to receive PostgreSQL updates.
  • You can now optionally upgrade your Jobserver running on Linux to use PostgreSQL 11. For more information, go to PostgreSQL 11 upgrade

New features

Data Lineage and BI integrations

  • Collibra Data Lineage now supports the Power Query M function Table.Combine. If Collibra Data Lineage can’t determine the column names in multiple sources, a dummy column with the value “*” is now created in the sources and Power BI tables, which preserves the technical lineage at the table level. For complete details, see Supported Power Query M functions. If you use this function, Table.Combine function is used. You can now view a technical lineage at the table level, where previously analyze error “Cannot determine source table for column”.

Miscellaneous

  • In Collibra Platform 2023.01, we have upgraded to PostgreSQL 11.17 to ensure that your Collibra can continue to receive PostgreSQL updates.
  • You can now optionally upgrade your Jobserver running on Linux to use PostgreSQL 11. For more information, to PostgreSQL 11 upgrade.

Enhancements

Data Catalog

  • You can now configure the database registration via Edge with the Catalog Experience setting disabled.
  • For performance reasons, we collect sample data for a maximum of 1,500 columns per table via Edge. If more columns are available, no sample data is collected for them.

Data Lineage and BI integrations

  • Improved error message formatting when viewing source code in the Transformations table of the technical lineage Sources tab page.
  • If a Tableau worksheet is hidden in Tableau, the “Visible on server” attribute of the Tableau Worksheet asset in Collibra now has the value false. If it is not hidden, the attribute has the value true.
  • When you integrate Power BI, the technical lineage now correctly shows a yellow background when columns and tables are stitched.
  • When you ingest SQL Server Reporting Services (SSRS) and set the “useCollibraSystemName” property to “true”, SSRS now has its own node in the navigation tree of the Technical lineage Browse tab pane.
  • Collibra Data Lineage service now supports the Power Query M function Value.NativeQuery. (ticket #98255)
    Note Query parameters are supported, but core parameters are not.
  • When you ingest Oracle data sources using the DatabaseOracle source type, passwords are now stored per URL, user name and database instead of just URL and user name. With this enhancement, you can connect to Oracle Pluggable Databases, for which a single user can have the same username and different passwords for each of their pluggable databases.
  • For Informatica PowerCenter technical lineage, when a PowerCenter mapplet had an associated shortcut, technical lineage in Collibra would be broken up. Now, there is end-to-end lineage within PowerCenter even when a mapplet has an associated shortcut.

Data Marketplace

Fixes

Data Catalog

  • Database registration via Edge now replaces the UTF-8 NULL character with an empty character unless it appears in the name of the asset. In that case, the database registration will report an error. (ticket #98765)
  • The Technical Data Type is now visible on the Details tab of the Tableau Data Attribute asset. (ticket #96703)
  • The Catalog JDBC Profiling capability has been updated. Columns with unsupported data types are now excluded from profiling queries. The exclusion applies to columns mapped to following java.sql.Types: ARRAY, BINARY, BLOB, CLOB, DATALINK, DISTINCT, JAVA_OBJECT, LONGVARBINARY, NCLOB, NULL, OTHER, REF, REF_CURSOR, ROWID, SQLXML, STRUCT, VARBINARY. (ticket #100005)

Data Lineage and BI integrations

  • Fixed a ValidationError related to the unsupported Exasol dialect. The Postgres dialect is now used in place of Exasol dialect. (ticket #98493)
  • The data type for Measures is now Number. Previously, it was Unknown. (ticket #98395)
  • When you integrate Tableau:
    • Metadata batches no longer fail if CREATE TECHLIN VIEW statements fail due to analysis errors. (ticket #97831)
    • Collibra Data Lineage service benefits from improved parsing of BigQuery quoted identifiers, for example `a.b`.`c`. (ticket #97831)
    • If you don't have permissions to access a parent project, but the lineage harvester identifies published data sources that belong to the project, the lineage harvester creates an ‘Unknown project’ that has the UUID of the inaccessible parent project. To avoid an error, the lineage harvester can now correctly link the published data sources to the unknown project.
  • When you integrate Power BI or Azure Data Factory (currently in public preview), the lineage harvester now connects to the Microsoft cloud instance, instead of the login.microsoftonline.com host.
  • When you integrate Power BI and use a <source ID> configuration file, you no longer have to include the filters section.
  • Tableau filtering now works as intended. Previously, filtering didn't work if you moved an older Tableau project under a newer project. (ticket #101594)
  • Fixed the ordering of columns for Tableau technical lineage custom queries. (ticket #99890)
  • The “Document size” attribute type and value is now shown for Tableau Workbook assets. (ticket #101703)
  • Tableau Data Attributes are no longer shown twice — once with the UUID in the name and once without — in the technical lineage Browse tab pane. (ticket #102865)

Data Governance

  • The table is now automatically updated when an attachment is uploaded in the Files tab of a community or domain page. (ticket #102240)
  • You now correctly see the 10 latest results for each tab when using Global Create for the homepage, Data Marketplace and Usage Analytics.
  • When trying to import an update to an existing asset, domain or community using the new import wizard, the import no longer fails if the asset or domain type is not mapped.
  • An error message no longer appears if you delete a dashboard immediately after creating it. (ticket #92785, 97186)
  • The Counters widget now correctly counts the Tableau assets. (ticket #94063)
  • If no dashboards are available to you, a meaningful error message is now shown, with a button to create a dashboard, depending on your permissions.
    Note To create a dashboard, you must have one of the following global permissions:
    • Manage shared Views, Dashboard and Search Filter
    • Manage your own Views, Dashboards, Search filters
    (ticket #87671)
  • The Refresh icon in a table with hierarchy enabled now correctly reloads the data in the table. (ticket #93767)
  • If automatic hyperlinking is enabled and the processing of hyperlinks fails, Collibra no longer infinitely reattempts the processing, to prevent spamming the error log. (ticket #93889)
  • If you open a different view in a new tab or window from the views page, the correct view now opens instead of the current view.
  • If you load an asset page that contains a relation table with sorting on a column that represents another relation type, and if that relation type is deleted, an error message no longer appears. (ticket #95918)
  • The Dashboards card in the homepage now truncates dashboard names with long strings.
  • The Organization tab in the Browse pane of the homepage, Data Marketplace, and Usage Analytics now shows all the top-level communities instead of only the first 100.

Diagrams

  • After opening a picture, if you navigate away from the Pictures tab and then go back to the Pictures tab, the picture that you last opened no longer appears. Instead, the list of pictures appears. (ticket #96923)

Edge

  • Fixed an issue where Edge sites with a "man-in-the-middle" proxy using a custom certificate could not communicate with Collibra after the server was restarted.

API

  • Collibra now validates the dashboard ID parameter when creating a dashboard using the REST API. (ticket #96595)

Miscellaneous

  • To enhance the security of Collibra, this release includes mitigations for multiple log4j vulnerabilities. (ticket #99012, 95708)