Release 2022.04

• Release information
• Metamodel changes
• Enhancements
• Fixes
• Hotfixes

Release information

• Release date of 2022.04.0: April 10, 2022
  • Upgrade non-production environments: April 10, 2022
  • Upgrade production environments: May 1, 2022
• Release date of 2022.04.1: May 8, 2022
• Relevant Jobserver version: 2022.2.3-58

Metamodel Changes

• We have renamed the S3 Catalog domain type to Storage Catalog.
• We have added the flowing new out-of-the-box asset types:
  
  • File Container: An asset type that represents Cloud File Container as a subset of Technology Asset.
  • GCS Bucket: An asset type that represents a Google Cloud Storage bucket as a subset of Technology Asset → File Container.
  • File Storage: An asset type that represents a Cloud File Storage bucket as a subset of Technology Asset → System.
  • GCS File System: An asset type that represents Google Cloud Storage file system as a subset of Technology Asset → System → File Storage.
• We have moved the following out-of-the-box asset types:
  
  • Directory is now a subset of File Container.
  • S3 Bucket is now a subset of File Container.
  • S3 File System is now a subset of File Storage.

Enhancements

Data Catalog

• You can now use partial scan to profile most columns of Impala data sources via Edge, except for those in views, Kudu tables, and HBase tables.
• You can now configure the maximum number of rows used by the Edge classification service in the "Maximum number of samples" field. See Configure data profiling behavior.
• You can modify the resource and CPU assignments of a data source by adding additional properties to the Catalog JDBC Ingestion Edge capability. We recommend to only add these properties together with Collibra Support. See Add an capability to an Edge site.

Data Lineage and BI integrations

• Collibra Data Lineage now supports calculated fields for embedded data sources that are published.
• You can now use a databaseMapping property in your Tableau <source ID> configuration file, to map a Tableau technical database name to the real database name.

Search

• The Status facet is now a multi-select facet, meaning that when you are filtering search results, you can now simultaneously filter on more than one asset status.

Security

• The user input in the default email templates is now encrypted. Unsafe characters are replaced with safe versions.

Miscellaneous

• Azul Zulu JRE (Java Runtime Environment) is updated to version 8.0.322. Jobserver has also been upgraded to version 2022.2.3-58 to support this JRE version. (ticket #83442)

Fixes

Data Catalog

• Attributes containing plain text with special characters (<>) now expand correctly in tables, also when Catalog experience is disabled. (ticket #72613)
• If you modify the refresh schedule or the profiling / sampling options of Schema assets, Collibra no longer tests the connection to the data source via Jobserver. (ticket #77126, 80740)
• If you try to synchronize a Database asset with no assigned Owner, Collibra now shows an adequate error message. (ticket #81206)
• Jobserver jobs that fail during the finalization step now receive the status Failed instead of running indefinitely. (ticket #82221)

Data Lineage and BI integrations

• The lineage harvester now supports InOut parameters for mapping tasks when harvesting metadata from Informatica Intelligent Cloud Services data sources. The parameters are now loaded and their values are used to replace variables in custom SQL queries. (ticket #80090)
• After synchronizing a data source, the time is now accurately shown in the Last sync time column on the Sources tab page. (ticket #82213)
• When providing connection definitions for Informatica PowerCenter, the dbname property is no longer case-sensitive. (ticket #81810)
• When harvesting parameter files in Informatica Intelligent Cloud Services data sources, parameters (including those with numbers in their names) in SQL overrides are now correctly matched. (ticket #73786)
• The display name for Looker Data Set assets now uses the 'label' property, which provides an easier-to-read name.
• When integrating Informatica PowerCenter, Collibra Data Lineage now correctly creates a technical lineage when useCollibraSystemName is set to true. (ticket #81721)
• The ingestion of Tableau Worksheets and Tableau Dashboards no longer results in an error when the external system ID already exists in Data Catalog.
• Fixed an issue that resulted in a parsing error indicating that the useCollibraSystemName property was set to “true”, when it was set to “false”. (ticket #82448)
• When integrating Informatica PowerCenter, Collibra Data Lineage now replaces parameters starting with a single "$" inside extracted queries. (ticket #83807)
• Fixed an issue in the lineage harvester that was causing random occurrences of newline characters in ingested Teradata objects.
• The Teradata JDBC driver is now upgraded to version 17.10.00.27.
• The MySQL JDBC driver is now upgraded to version 8.0.28.
• Fixed an issue in the REST API pagination.
• The Collibra Data Lineage servers now benefit from the following parsing enhancements when integrating Snowflake data sources (ticket #85490):
  • Support for CONNECT BY after WHERE clause.
  • Support for TOP.

Data Governance

• Fixed an issue with the pagination of asset tables when you open the preview pane.
• The Pictures table once again refreshes automatically.
• The Automatic Hyperlinking feature now handles special characters such as hyphens and slashes better. (ticket #80158)
• You can once again clear date attributes using the Clear button. (ticket #77838)
• You can once again open communities in a new tab page from a link. (ticket #80081, 81342)
• Fixed an issue with the Load More button on the History page.
• In the history of a community, domain or asset, if you select a user other than the signed-in user as the Who filter, and then apply an Action filter, the history of the selected user is now shown, instead of the signed-in user.
• You can now only create assets in a domain whose type is allowed in the asset type's assignment. (ticket #72942)
• Fixed an issue which caused incorrect Last Login data time to be shown in exported CSV.
• Fixed an issue in the Complex Relation Type field when importing complex relations. (ticket #75736)
• Fixed an issue with inherited permissions, where all relevant domains are again available when moving assets. (#81272, 81501, 81592, 81612, 81727, 81794, 82017, 82327, 82418, 82630, 83593, 83601, 83922, 83970, 84768, 84828, 85060, 85470, 85572)

Diagrams

• Diagram overlays and the Preview pane now show dates in the same time zone. (ticket #78000)
• Sharing diagram pictures no longer results in an error.

Security

• A CSRF token is no longer missing from the response when no cookies are set for the auth/session API. (ticket #83781, 83808, 83822, 83862, 83892, 83920, 84009, 84054, 84164, 84182, 84455, 84767)

API

• Τhe REST API endpoint GET/responsibilities now returns the expected results when specifying "type=RESOURCE". (ticket #69322)
• Retrieving relations or complex relations in batches using the REST or Java APIs no longer creates overlapping content in the results. (ticket #80323)
• You can again use the 'BETWEEN' filter in the Output Module. (ticket #83068, 83202)

Hotfixes

Collibra 2022.04.1

• You can now profile schemas via Edge that include more than 1,000 tables. (ticket #86838, 87179)
• Asset tables can again accommodate more than 10,000 assets. (tickets #81689, 85774, 86242, 86315, 86529, 86614, 86657, 86660, 86717, 86887, 87492, 87535)

Lineage harvester hotfix 1

• The lineage harvester no longer hangs when harvesting metadata from certain data sources.
• The Apache Hive JDBC driver is now upgraded from 2.6.17.1020 to 2.6.19.2022.
• The PostgreSQL JDBC driver is now upgraded from 42.3.2 to 42.3.3.
• The lineage harvester automatically refreshes Tableau tokens. (tickets #82323, 85617)
• You can now use the optional concurrencyLevel property in the lineage harvester configuration file, to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. (tickets #82323, 85617)

Edge capability hotfix 1

• When you specify an invalid region name in the AWS region restriction console configuration, an error is now reflected in the logs.
• At the start of an S3 synchronization process, the search for previous AWS Glue databases now respects the AWS region restriction rules.