Release 2023.07

• Release information
• Enhancements
• Fixes
• Collibra maintenance updates
• Edge updates

Release information

• Release date of Collibra 2023.07.0: July 9, 2023
  • Upgrade non-production environments: July 9, 2023
  • Upgrade production environments: July 30, 2023
• Release date of Collibra 2023.07.1 (with Java 17.0.6): July 28, 2023 (GovCloud environments only)
• Release date of Collibra 2023.07.1 (with Java 17.0.8): August 31, 2023 (GovCloud environments only)
• Release date of Collibra 2023.07.1 (with Java 17.0.8): On demand only
• Release date of Edge 2023.05.1: May 21, 2023
• Release date of Edge 2023.05.2: June 4, 2023
• Release date of Edge 2023.05.3: July 2, 2023
• Release date of Edge 2023.05.4: July 9, 2023
• Release date of Edge 2023.05.5: July 16, 2023
• Release date of Edge 2023.05.6: July 30, 2023
• Relevant Jobserver version: 2023.05.0-55

Highlights

• Collibra Data Lineage
• Collibra Data Lineage now supports the following Power Query M functions:
  • Cube.Transform
  • Cube.AddAndExpandDimensionColumn

  These functions enable technical lineage between SAP HANA (using SapHana.Database) and Analysis Services (using AnalysisServices.Databases), and improve the success rate of metadata analysis.

Enhancements

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• When you create technical lineage for Snowflake with the SQL-API ingestion method, you can use the displaySampleQueries property in the new Snowflake source ID configuration file to control whether a question mark (?) is displayed in place of certain static values, such as numbers or dates.
• When ingesting Spark SQL data sources, the Collibra Data Lineage service instances now support PARTITIONED BY parameters in CREATE TABLE statements.
• Collibra Data Lineage now supports the following Power Query M functions:
  • Table.FromList
  • AnyalysisServices.Databases
• When you create technical lineage for Matillion, the lineage harvester now supports multiple data sources. Previously, the lineage harvester could only generate technical lineage from one source.
• When you create technical lineage for Informatica Intelligent Cloud Services and set the useCollibraSystemName property as true, the Collibra system name is used as root of the tree in the technical lineage graph. Previously, IICS was used.
  See an example.

  
• When you create technical lineage for Azure Data Factory, global parameters are now taken into consideration.

Assessments

• The Collibra Assessments documentation now contains a video that shows how to set and change the permissions of an assessment.

Fixes

Data Catalog

• The "Register Source Tags" option is no longer set to True for data sources that do not support the feature. (ticket #114309, 115336)
• If conflicts occurred during the refresh of a schema with Jobserver and you refresh the schema again, the activity now correctly reports the conflicts again instead of remaining in the Waiting status. (ticket #115168, 117018, 115879, 116737, 114744, 117989, 119373)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• When you create technical lineage for SQL Server Integration Services (SSIS), the Source code panes in the technical lineage graph are no longer named as None. Previously, certain Source code panes were labeled as None, but now query names are used instead. (ticket #110889)
• SQL Extension now supports queries that have a WITH clause.
• When ingesting Oracle data sources, the Collibra Data Lineage service instances now correctly handle database links even when the remote database has a dot (.) in the name. (ticket #114056)
• When ingesting Snowflake data sources, the Collibra Data Lineage service instances now benefit from the following parsing enhancements:
  • Undocumented usage of UPDATE FROM statement, when the FROM clause comes before the SET clause.
  • IDENTIFIER keyword appears as a column name. (ticket #112812)
• The 404 not found error no longer shows in the Technical Lineage tab if the error is caused by unfinished synchronization of the technical lineage. (ticket #113681)
• When integrating MicroStrategy, any facts that don't have expressions are now skipped. Previously, Collibra Data Lineage attempted to process such forms, which resulted in errors. (ticket #117264)
• When ingesting Netezza data sources, the Collibra Data Lineage service instances now support EXTERNAL from item.

Data Governance

• When importing previously exported assets, the import wizard maps again correctly the tag attributes.
• At the end of a successful import that started from a community or domain page, you can again see the newly imported assets on the page without the need to refresh it.

• Newly created internal sysadmin users, that are not yet activated, are now able to set their password and complete their account activation.

• Fixed security vulnerability of HTML injection during new user creation which can be used in content spoofing.

• Fixed an issue that allowed people to check the validity of an email via account recovery. You will now see the same message whether the email address used is linked to an account or not.

Assessments

• You can now work on an assessment or a template for an extended period without being automatically signed out, provided that you actively engage with the page (for example, by clicking, scrolling, or typing). This enhancement allows you to work without the disruption of being unexpectedly signed out. (ticket #109715)

Security

• You will now be redirected to the sign-in page if your session expires, this is to fix a security vulnerability that would have previously potentially allowed sensitive information to be exposed if you were viewing it when the session expired. (ticket #96498)

Collibra maintenance updates

Collibra 2023.07.1

• Fixed a cross-site scripting vulnerability.
• To improve security, we have upgraded Java to version 17.0.8.

Edge 2023.05.6

• We have improved the security of Data Classification via Edge.
• The S3 synchronization capability has been updated to prevent any null pointer exception.