Release 2022.09

• Release information
• Highlights
• Enhancements
• Fixes
• Features in preview
• Hotfixes

Release information

• Release date of 2022.09.0: September 11, 2022
  • Upgrade non-production environments: September 11, 2022
  • Upgrade production environments: October 2, 2022
• Release date of 2022.09.1: October 2, 2022
• Relevant Jobserver version: 2022.08.1-56

Highlights

• Previously, when you created a technical lineage for Power BI, SQL Server Reporting Services (SSRS) or Power BI Report Server (PBRS), the nodes in the technical lineage graph had a gray background, even if the data objects from your data source were stitched to assets in Data Catalog. Data objects now have the intended yellow background when creating a technical lineage for Power BI, SSRS or PBRS. We introduced this enhancement for Tableau and Looker in Collibra 2022.07.

Enhancements

Data Lineage and BI integrations

• Improved processing times for data flows when integrating Power BI.
• When ingesting Informatica PowerCenter data sources, for transformations that have a DESCRIPTION value, the DESCRIPTION value is now shown at the last line of the transformation to which the description is applied.

Miscellaneous

• The Azul Zulu Java package is upgraded to version 11.0.16. (ticket #90270, 93428)
• The org.springframework.boot version for the data-classification-controller component has been updated to 2.5.14 to remediate CVE-2022-22965. (ticket #92239)

Fixes

Data Catalog

• You can now register an Oracle data source with a service name that contains @ # $ _ . or - via Edge. (ticket #90951)
• The Data Classification tab now shows all data classes, including the data classes created by users who are deleted. (ticket #87166)
• Fixed the issue with S3 synchronization via Jobserver that was caused by connection issues on HTTP level. (ticket #90141, 91640)
• When ingesting Informatica PowerCenter data sources, Collibra Data Lineage now supports the orveriding of SQL queries by Powercenter Session level attributes. (ticket #92247)

Data Lineage and BI integrations

• When you integrate Tableau:
  • If you use domain mapping, subprojects are now ingested in the domains of their parent projects. (ticket #93071)
  • For every Tableau Workbook that you have permission to ingest, all Tableau Dashboards in the Workbooks are now correctly shown in the technical lineage graph. If you do not have permission on the Workbook or Dashboard level, the metadata of these data objects is not ingested. (tickets #90508, 91225)
  • You can now ingest subprojects for which you have permission to ingest, even if you don’t have permission to ingest the parent projects. (ticket #90508)
• When you integrate Power BI:
  • The descriptions of Data Set Tables and Data Set Columns in Power BI are now harvested. (ticket #92736)
  • The lineage harvester is now more resilient to OutOfMemory errors. (tickets #93502, 94681)
• When you integrate SQL Server Reporting Services (SSRS) or Power BI Report Server (PBRS) data sources, relations between SSRS assets are again correctly created and shown in the technical lineage graph. (ticket #88100)
• When you integrate an Oracle data source, the value of the "databaseNames" property in your lineage harvester configuration file must be either the Oracle SID or service name, depending on whether you set the "connectAsServiceName" property to "true" or "false". This means that the database in the technical lineage will have the name of the Oracle SID or service name. However, if the database asset in Data Catalog reflects the true name of the database, stitching will break. To resolve this issue and preserve stitching, you need to rename the database asset in Data Catalog to match the value you put for the "databaseNames" property. This is a known issue that we will fix in a future release.
• The Collibra Data Lineage service instances now support the WITH UR clause when integration Oracle data sources. (ticket #89528)
• Informatica PowerCenter scanner now stitches correctly for mapping overrides for ETL targets. Previously, it stitched to the wrong assets in Data Catalog.
• The Collibra Data Lineage service instances now benefit from the following parsing enhancements when integrating Snowflake data sources:
  • Support for the COLLATE keyword.
  • Support for EXTERNAL TABLE syntax.
  (ticket #92196)
• Fixed an issue that was resulting in a processing error when a column referenced in an ORDER BY clause references a repeated column in the SELECT column list. (ticket #92330)
• The Add to Data Basket button is again available for Power BI Report (or children) assets. (ticket #89409, 91978)
• The PostgreSQL JDBC Driver is upgraded to version 42.4.1. (ticket #94706)
• When integrating Snowflake data sources, the value of the collibraSystemName property in the lineage harvesterconfiguration file is now correctly taken into account. (ticket #94314)

Data Governance

• If a community or domain for which you don't have view permissions is used in a criterion of an asset filter, then you cannot edit the filter and don't see the criterion.
• If you switch between single-path and multi-path hierarchy in an asset table, you no longer have to refresh the page to see the new hierarchy.
• The order of widgets on a dashboard now stays the same after refreshing the page. (ticket #84353)
• You no longer see code if you scroll down on certain dashboards. (ticket #94298)
• The Output module once again returns responsibilities for non-administrator users if Enable joins for view permission filtering is enabled. (ticket #90057, 90829, 91185)
• When importing assets or complex relations, testing the import no longer fails if the user interface language is not set to English. (ticket #91500)
• You now only see the Actions menu on a community or domain page if you can do at least one of the listed actions.
• Fixed an issue where the title was missing from the attribute dialog box when adding an attribute as a characteristic on an asset page. (ticket #94997).

Diagrams

• If you add an edge to a node in a diagram, the value that you select in the Relation Type field (for example, Technology Asset is system of record for Business Asset) no longer disappears. (ticket #88544)
• The preview pane in a diagram once again shows the correct ratings of the selected asset. (ticket #89769)
• If you open another node from a diagram using Start here and select the current diagram view, Collibra no longer stays on the current asset but opens the diagram starting from the selected node. (ticket #90567, 92496, 94901)

Collibra Console

• Fixed an issue that prevented new users who were created in Collibra Console from changing their password via the link within their initial confirmation email. (tickets #90311, 90831, 91223, 91348)
• Fixed an issue with SSO that caused Collibra Console to crash because of a memory leak. (ticket #93202, 93244, 93273, 93378, 93442, 93539, 93868, 94056, 94166, 94215, 94545, 94596, 94701, 94768, 95607, 95812, 96417)

Miscellaneous

• If you switch between views on the Assets tab page of a community, the view ID in the URL is now updated correctly.

Data Marketplace

• If Analytics are enabled in your Collibra environment, the Data Marketplace landing page shows Popular Data and Recommended Data, instead of Recent Searches and What's New. See The Data Marketplace landing page.
• Fixed an issue where Tags were incorrectly mentioned to match the search in the Search results.
• Fixed an issue where only the first 50 statuses were available for selection in the Data Marketplace scope.
• You can select all asset types via the Select all checkbox in the Data Marketplace scope.
• The Search field is now cleared when search suggestions are enabled and you click the X icon.
• The Primary Action label now shows the start label of the selected workflow definition instead of the name attribute of the workflow.

Hotfixes

Collibra 2022.09.1

• If a network issue occurs while registering a JDBC data source via Jobserver, Collibra again retries repeatable network requests. (ticket #87158)
• Collibra once again works in Safari, and Collibra Everywhere works again on devices running on iOS.
• If your administrator specifies a new password or generates a new password automatically, you no longer receive an email containing your password. Instead, your administrator should provide you with the password.
• Filter clauses with 'exists' and 'does not exists' operators work again in the Advanced Filter pane. (ticket #97050, 98143)