Only show release notes of Collibra Platform for Government-certified featuresRelease 2022.06
Release information
- Release date of 2022.06.0: June 5, 2022
- Upgrade non-production environments: June 5, 2022
- Upgrade production environments: June 26, 2022
- Release date of 2022.06.1: June 24, 2022
- Relevant Jobserver version: 2022.05.1-67
Highlights
- A key feature of the Collibra Platform 2022.05 release was the ability to ingest Power BI metadata in Data Catalog via the lineage harvester, meaning you no longer need to use the Power BI harvester. However, the new integration method was only available to customers who did not need to migrate existing Power BI assets. With this release, you can now migrate your existing Power BI assets, making integration via the lineage harvester available to all Power BI customers.
Enhancements
Data Lineage and BI integrations
Note Data Lineage is a cloud-only feature.
- The UUIDs of Tableau Data Attribute assets are no longer included in the asset name and full name.
- When ingesting Power BI, if there are Oracle data sources, the Oracle service name is now used, instead of the database name.
- You can now export technical lineage information to a JSON file, via the Settings tab pane.
- When integrating Power BI, you can now ingest measures without DAX. They are shown as attribute type Role in Report on Power BI Column asset pages.
Edge
Note Edge is a cloud-only feature.
- Host exposure to pods is limited to the OpenTelemetry and DataDog agents. These agents have read-only access to the host file system which is required to read the logs from the pods.
- When you specify an invalid region name in the AWS region restriction console configuration, an error is now reflected in the logs.
Fixes
Data Catalog
- Collibra can now profile large Teradata data sources via Edge without numeric overflow error. (ticket #81572)
- In a Column asset, the Personal Identifiable Information (PII) and Primary Key icons are now displayed correctly. The Personal Identifiable Information (PII) icons indicate whether the column contains personal information. The Primary Key icon is displayed only if the column has been identified as the primary key. (tickets #81942, 82737, 84021)
- Technical lineage is now available for Database views. (ticket #84155)
- The Description field in the Summary of asset pages now shows the correct value. (tickets #85164, 83843)
- The description provided during the XLS or CSV registration is now saved and visible in the Schema Summary and Details pages.
- You can now profile schemas via Edge that include more than 1,000 tables. (ticket #86838, 87179)
- The Row count in the Summary tab of Table assets now displays the correct number. (ticket #86546)
- It is now possible to synchronize a specific schema in a database, even if the database contains more than 40,000 schemas. (ticket #87956)
- It is now possible to bulk synchronize a database, even if the database contains more than 40,000 schemas. (ticket #87387)
Data Lineage and BI integrations
Note Data Lineage is a cloud-only feature.
- The Collibra Data Lineage servers now benefit from the following parsing enhancements when integrating BigQuery data sources:
- UNNEST WITH OFFSET expressions. (ticket #88048)
- INFORMATION_SCHEMA qualifiers. (ticket #87531)
- The Collibra Data Lineage servers can now parse ":" infix function and stage files with path in FROM clause, when integrating Snowflake data sources.
- Fixed an issue in the Collibra Data Lineage servers that was affecting the processing of Tableau Data Attributes.
- When processing Tableau metadata, the Collibra Data Lineage servers no longer replace ">>" by "<}", which was resulting in parsing errors. (ticket #87185)
- When ingesting SQL Server Integration Services metadata, the Last Sync Time column on the Sources tab page now correctly shows the time stamp, instead of showing "none". (ticket #85610)
- Fixed an [SQLITE_ERROR] issue that was breaking the technical lineage when attempting to synchronize a data source. (ticket #85541)
- When processing Power BI metadata (for Oracle data sources), SQL statements are now in upper case.
- When creating a technical lineage for Tableau, any unnecessary brackets “][“ in the names of schemas are now removed.
- 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.
- Fixed an issue in the script for migrating Tableau assets to the new operating model.
- Fixed an issue that was causing the processing of harvested metadata batches to run without coming to completion. (tickets #86480, 88205)
- Fixed potential "show Locks LockManager not specified" error when ingesting HiveQL.
- Changed a web server configuration to support uploading of ZIP files larger than 2 GB. (ticket #87837)
Data Governance
- You can once again switch between views without saving changes. (ticket #85042)
- The column order of an export using "Add the characteristics needed for reimport" option is correct again. (ticket #83530)
- You no longer get a DataFetchingException error if historical guest users exist in the database and you open the Users page. (ticket #87959, 88857)
Assessments
- If you download a PDF of an assessment, the PDF now correctly shows Multiline Input question types and responses. (ticket #76495)
- If you download a PDF of an assessment that was based on a template that has a Decision question type, the decision is now shown in the PDF.
Edge
Note Edge is a cloud-only feature.
- The lineage harvester on Edge now logs all errors from the load source phase.
- At the start of an S3 synchronization process, the search for previous AWS Glue databases now respects the AWS region restriction rules.
Security
- When lock-out duration is disabled, your account is now correctly locked out after unsuccessful sign-in attempts.
- Generated passwords now always comply to the password policy.
- Your Collibra session now closes correctly when the session times out. (ticket #65867, 83973, 87289)
Hotfixes
Collibra 2022.06.1
- Fixed an issue that prevented Collibra to start if there are jobs scheduled with a Cron pattern, for example to start synchronizing, profiling or classifying a data source. (ticket #88808, 89602, 89938)
- Asset pages now load correctly if the asset name contains special characters. (ticket #89075)
- Asset views once again show assets if you start sorting or filtering while the set of tiles or table is still loading. (ticket #87548, 87617, 87706, 87869, 87997, 88333, 88397, 88802, 88892, 88938, 89030, 89554, 89750, 90066)
- You no longer get an error message if you try save the connection details with the optional fields left empty in S3 File System assets. (ticket #89366)