Release 2022.07

• Release information
• Highlights
• New features
• Enhancements
• Fixes
• Hotfixes

Release information

• Release date of 2022.07.0: July 10, 2022
  • Upgrade non-production environments: July 10, 2022
  • Upgrade production environments: July 31, 2022
• Release date of 2022.07.1: July 31, 2022
• Relevant Jobserver version: 2022.05.1-67

Highlights

• Previously, when you created a technical lineage for a supported BI tool, 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 Tableau or Looker. Soon, this will also be true for Power BI and SSRS-PBRS.
• The "collibraSystemName" property in the lineage harvester configuration file is deprecated.
  
  Note 

  • If you leave this property in your configuration file, it is ignored.
  • If "useCollibraSystemName" is set to "true", the "collibraSystemName" specified in the <source ID> configuration file is taken into consideration. If it is set to "false", the "collibraSystemName" in the source ID configuration file is ignored.

Enhancements

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• Collibra Data Lineage now supports assets with UUIDs.
• On the technical lineage Settings tab pane, performance is improved when you click the Show status button to switch to the Sources tab page. (ticket# 90359)
• The lineage harvester log file now includes the following information:
  • Your Tableau environment type: Tableau Online or Tableau Server
  • The version of your Tableau environment
• The collibraSystemName property is no longer required in BI and ETL tool sections of the respective configuration files. Instead, the Collibra system name should be specified in the <source ID> configuration file.
• You can now use the optional useSharedDbModel property to enable the sharing of metadata batches from multiple SQL data sources. This helps to avoid potential analysis errors on the Collibra Data Lineage server.

Fixes

Data Catalog

• The Description from source system field in the Table asset page now shows text without formatting because it is a Plain Text attribute. (ticket #87558)
• Scheduled jobs for synchronizing, profiling and classifying a data source or Amazon S3 no longer fail and prevent the DGC service to start. (ticket #88808, 89602, 89938)
• When synchronizing Amazon S3, the JSON request that is sent to the Import API is now saved in Collibra so that it can be used for troubleshooting. (ticket #81981, 84506, 86800, 88446)
• 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)
• Table and column assets in domains with restricted View permissions can now be profiled via Edge. (ticket #88149)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• The lineage harvester now retries to get a batch status if the first HTTP call failed due to a network error.
• When the lineage harvester fetches an access key for a data source, only active records are now fetched. Inactive records are ignored. (ticket #88388)
• Lineage harvester error message MSG-LIN-3005, “Fiber error on Snowflake”, is now raised and included in the technical lineage logs. (ticket #86009)
• Tableau scanner now excludes external mappings for hidden assets from Data Catalog. This is an incremental step toward completely removing hidden assets and relations. (tickets #84759, 88151, 88476, 88926, 89903)
• The lineage harvester is more resilient against authorization expiration when ingesting Looker metadata. (ticket #87429)
• Fixed an issue that was resulting in the No asset matches the specified criteria error.
• Collibra Data Lineage now supports Row Access Policy in Snowflake CREATE TABLE/VIEW statements. (ticket #88995)
• Collibra Data Lineage now supports worklets contained in other worklets with the same name, when ingesting metadata from Informatica Intelligent Cloud Services. (ticket #90234)
• Classic Power BI workspaces can now be identified by the suffix "[cPBWS]", to maintain the uniqueness of names. With this fix, filtering works as intended. (tickets #88990, 89830, 90085, 92356)
• Fixed an issue that resulted in a processing error when integrating MicroStrategy. (ticket #90048)
• The Collibra Data Lineage servers now support parsing of single-table INSERT OVERWRITE INTO statements when ingesting Snowflake metadata. (ticket #89228)
• Fixed an issue with Power BI Table external entity IDs. Power BI Tables are now shown in the technical lineage. (ticket #89542)
• To keep from exceeding the character limits for external system and entity IDs, a hash is now used instead of composed names for Power BI Tables, Power BI Columns and Power BI Capacities. (tickets #89355, 89423)
• The Collibra Data Lineage servers now skip Excel SQL statements, as they are not supported. (ticket #88424)
• Fixed an issue that was causing custom SQL queries to be identified as belonging to two different Tableau data sources. This resulted in a "Unique constraint failed" error. (tickets #90617, 90631)

Data Governance

• 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)
• If you use an asset filter to filter on a relation, the filter criterion no longer shows the full name but stays on the name. (ticket #88224)
• You can once again scroll correctly on asset pages. (ticket #86957, 87461, 87953, 88606, 88628, 89367, 89958, 90086, 90296, 90668, 91384, 91448)
• The Back button of your browser now works correctly in the Global View. (ticket #82527)

Search

• You can again search in fields, select various relation types, and edit your field selection without experiencing errors.

Hotfixes

Collibra 2022.07.1

• If you have two or more users with the same first and last names, you can once again add them simultaneously to the same group, or assign them to a global role or a responsibility in one go. (ticket #90911)