Release 2022.10

• Release information
• Enhancements
• Fixes
• Beta features

Release information

• Release date of 2022.10.0: October 9, 2022
  • Upgrade non-production environments: October 9, 2022
  • Upgrade production environments: October 30, 2022
• Release date of 2022.10.1: October 30, 2022
• Relevant Jobserver version: 2022.08.1-56

Enhancements

Data Lineage and BI integrations

• The lineage harvester now supports the following IBM DB2 constructs: PREVVAL FOR <sequence>, PREVIOUS VALUE FRO <sequence>, NEXTVAL FOR <sequence> and NEXT VALUE FOR <sequence>.
• The lineage harvester now supports a new optional "deleteRawMetadataAfterProcessing" property in your lineage harvester configuration file. With this property, you can delete your raw metadata from the Collibra Data Lineage service after processing. This property is applicable for all supported data sources.
  
  Note This property is not yet supported by the technical lineage backend, so it can't be used yet. Backend support is coming soon.
• The Collibra Data Lineage service now supports the following transformations: Table.FromRecords and Table.IsEmpty.
• Collibra Data Lineage now supports key-pair authentication when ingesting Snowflake data sources.
• The Collibra Data Lineage service instances now correctly ignore comments at the beginning of SQL statements.

Fixes

Data Catalog

• Fixed a query execution issue when using partial scan for BigQuery database profiling via Edge. (ticket #93094)
• The Frequency chart is now displayed in the Data Profiling tab page when the number of categories is smaller than two. (ticket #88593)

Data Lineage and BI integrations

• When you specify a Data Catalog URL in the lineage harvester configuration file, it no longer matters whether you include a trailing slash (/) in the URL.
• The PostgreSQL JDBC Driver is upgraded to version 42.4.1. (ticket #94706)
• The Collibra Data Lineage service can now compute indirect lineage from set queries, which are queries with the UNION keyword with the ORDER BY clause. (ticket #92330)
• When you integrate Power BI, the lineage harvester is now more resilient to OutOfMemory errors. (tickets #93502, 94681)
• When you integrate Tableau and filter on a sub-project, the metadata of the parent project is no longer ingested in Collibra. However, the parent Tableau Project asset is created in the default domain, to preserve the hierarchy required for stitching.
• Looker integration no longer fails if the "collibraSystemName" property is not included in the lineage harvester configuration file. If you want to specify the system name of a database in Looker, use the "collibraSystemName" property in the Looker source ID configuration file. If you don't specify a system name in the source ID configuration file, the system name in the technical lineage graph will be Default.
• In the case of a lookup procedure when ingesting Informatica Intelligent Cloud Services data sources, if the CONNECTIONSUBTYPE parameter is empty, the Collibra Data Lineage service now looks to the CONNECTIONREFERENCE parameter for the name. If that is also empty, then the name in the VARIABLE parameter is used. The ensures the correct detection of the SQL dialect. (ticket #92523)
• Fixed an issue related to dialect extraction when ingesting Informatica Intelligent Cloud Services data sources. (ticket #94239)

Data Governance

• Fixed an error that could occur if you have a complicated organization structure and while moving an asset you search for a domain which is part of a scope. (tickets #88984, #92169)
• You can once again create, edit and delete articulation score rules in the Global Assignment tab of an asset page without having to change the condition value of already existing articulation score rules.
• Filter clauses with 'exists' and 'does not exists' operators work again in the Advanced Filter pane. (ticket #97050, 98143)

Workflows

• When a workflow updates the status of an asset, you can again see the new status without having to manually refresh the page. (ticket #94441)

Miscellaneous

• Collibra once again works in Safari, and Collibra Everywhere works again on devices running on iOS.

Sample data

• Partial scan is now always used for sample data extraction via Edge if the data source supports it.

Hotfixes

Collibra 2022.10.1

• Fixed an issue where Edge sites on version 2022.10 could not communicate with Collibra. (ticket #99610, 99929, 100149)
• Apache Commons Text has been upgraded to version 1.10.

Edge capability hotfix 1

• The Catalog JDBC Ingestion capability has been updated to optimize the performance of the Teradata data source registration. (ticket #98696)