Release 2022.08

• Release information
• Highlights
• Metamodel changes
• New features
• Enhancements
• Fixes
• Features in preview
• Hotfixes

Release information

• Release date of 2022.08.0: August 7, 2022
  • Upgrade non-production environments: August 7, 2022
  • Upgrade production environments: August 28, 2022
• Release date of 2022.08.1: August 28, 2022
• Release date of 2022.08.2: September 11, 2022
• Relevant Jobserver version: 2022.08.1-56

Highlights

• Via the Edge SDK, capabilities can now read files from a shared folder on any cloud storage provider, for example K3S shared file system folder, Amazon S3, GCS or Azure - ABS.
• The asset pages of Tableau Worksheet, Power BI Report, and SSRS Report assets now have a Technical Lineage tab for viewing the lineage of a report.
• 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 Power BI. This enhancement was introduced for Tableau or Looker in Collibra 2022.07. Soon, the enhancement will also apply to SSRS and PBRS.
• You can now filter on the Tableau project level. This is a feature in preview.
• You can no longer create users with existing usernames ignoring casing, blank usernames or usernames with unsupported characters. Existing users with unsupported usernames are now reported in the log files.
• If you import assets or complex relations via the Import API, you can now use the continueOnError parameter. If you set this parameter and one or more resources lead to an error, the other resources will still be imported successfully.

Metamodel changes

• The out-of-the-box data classes for Automatic Data Classification were enhanced:
  • A new class "Canadian Postal Code" was added.
  • The "Email" class now allows for IP addresses in addition to domain names.
  • The "IP address" now allows leading zeros (0).
  • The "Phone number" class now allows dots (.) as separators.
  • The "SSN" class performance was improved.

• The “Policy Lifecycle Management” role has been introduced in 2022.05 release and renamed to “Protect manager” in 2022.08. This is a role for our system user to manage background processes and setup configurations for Collibra Protect, which is an upcoming product. We recommend to our customers to not use this roles at this point in time.

New features

Data Catalog

• When you profile and classify a data source via Edge, you now receive a report when the process is completed. See Edge profiling and classification report.
• The Workday Catalog connector is now certified for Edge.

Search

• You can now enable asynchronous indexing via the feature switch in Console. With asynchronous indexing enabled, the Search service processes changes to your environment in batches, or processing cycles. This helps to ensure optimal performance, especially after big changes to your environment.

Collibra for Mobile

• You can now tap the community or the domain displayed in the breadcrumb trail at the top of an asset page to view the respective community or domain page.
• You can now share a community or a domain. To facilitate this feature, is added to the community and domain pages.

Collibra Console

• You can now use the new configuration setting "Number of failed commands before stopping import job", which stops an import job with the option to continue on error after the specified number of commands have failed.

Security

• We now deploy CSP-RO (Content Security Policy-Report Only), which sends logs to Collibra if a CSP-RO rule is violated.

Enhancements

Data Catalog

• When you register a data source via Edge, the Data Source Type attribute of the resulting Database and Schema assets now contain the name of the actual data source instead of "Collibra driver".
• New REST APIs are available that allow customers to work with the Database Profiling via Edge feature outside of the UI.
• If a data source supports partial scan, partial scan will be the default option when configuring data profiling and classification. See Configure the profiling and classification options via Edge.
• You can now indicate via a schema-specific table rule that you do not want to profile and classify a schema via Edge. See Configure the profiling and classification options via Edge.
• S3 on Edge now shows interim synchronization results in the Activities page. See S3 on Edge documentation.
• S3 on Edge now adds a warning to the logs if an invalid region is detected in the restricted regions list.
• The S3 restricted regions mechanism has been enhanced to only consider the restricted regions instead of all regions before starting an ingestion. This means that, if you remove a region from the S3 restricted regions configuration and the region was previously used for an S3 ingestion, you may want to delete the Glue database from the previously used region manually. The Glue database has the following naming convention: collibra_catalog_<Asset Id>_<Domain Id>. For example: collibra_catalog_d3174a88-5ffe-4d50-8fbe-7bf0832ec3af_5d198ce9-4e56-4d0e-a885-58204da50741. See Restrict AWS regions.

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• When integrating Matillion, you can now configure a <source ID> configuration file, to define the system name for all sources and targets in the Matillion job.
• You can now prepare a Looker <source ID> configuration file, to specify which Looker Folders you want to ingest in Collibra.
• When integrating Looker, the ownership information (email address only) for folders, Looks and dashboards is now ingested in Collibra. The new Owner in source attribute is included on Looker Folder, Looker Look and Looker Dashboard asset pages.
• When integrating Power BI, the ownership information (email address only) for data sets and workspaces is now ingested in Collibra. The new Owner in source attribute is included on Power BI Data Model and Power BI Workspace asset pages.
• Tableau Site asset pages now show the relations to both projects and subprojects.
• When synchronizing Tableau, the synchronization no longer fails if two data sources in the same project with the same name are returned from the Tableau API. The assets of both data sources are now synchronized in Collibra.
• The lineage harvester log file now identifies whether you are using Tableau Online or Tableau Server, and the version of your Tableau environment.
• When integrating Power BI, you can now include the optional found_schema property in the databaseMapping section of your Power BI <source ID> configuration file, to map a schema that is used in Power BI to a Schema asset in Collibra, thereby preserving stitching.
• The prefix "[App]" in the name of a Power BI Report asset indicates that the report is included in an app in Power BI. Direct links to such reports in Power BI don’t work, therefore the URL attribute is no longer included on Power BI Report asset pages for such reports.
• When integrating Power BI, you can now ingest measures and show them in the technical lineage. Measures are included as the value in the Role in Report attribute on Power BI Column asset pages.
• When you specify the Power BI workspaces for ingestion, the filters are not case sensitive now.

Data Governance

• You can now see and copy the ID of a scope by expanding the scope tile on the Scopes page.
• You can now edit the Roles and responsibilities view in the Stewardship application. (ticket #85388)
• Assigning a responsibility to a group with a lot of users is now faster.
• You can no longer create users with existing usernames ignoring casing, blank usernames or usernames with unsupported characters. Existing users with unsupported usernames are now reported in the log files.
• Deleting domains containing assets with complex relations is now faster. (ticket #76864, 77356, 77550, 81203, 82723, 83977)
• You can now create and edit complex relations in fewer steps.
• On domain and community pages, the buttons for renaming, moving and deleting the domain or community, as well as starting a workflow, are now in the Actions menu in the title bar.

Data Privacy

• You can now disable the custom asset pages of the deprecated asset types CSA, DPIA and PIA. You can also disable the custom Business Process asset page. Disabling the custom asset pages removes the regulation-specific sections from the tab pane on the asset page.

Miscellaneous

• The Azul Zulu Java package is upgraded to version 11.0.16. (ticket #90270, 93428)

Fixes

Browser Extension

• Data auto-matching between your Tableau dashboard and your Collibra Platform environment no longer fails if your webpage address does not contain the Tableau site or workbook name. (ticket #89169)

Data Catalog

• Catalog asset pages now load faster even if the Catalog Experience setting is disabled. (ticket #71958, 76040)
• The database registration process via Edge now returns the correct schema name for databases that contain only one schema. (ticket #81495
• Fixed an issue where you could not synchronize a Database asset via Edge after renaming it. (ticket #81754, 81901, 85718, 86236, 86628, 90046,92517, 93391)
• In the configuration for S3 integration via Edge, you can now indicate you want to ingest File Group assets as File assets. This can prevent assets from being labeled as "Missing from source". (ticket #82820)
  See S3 on Edge documentation.
• The database registration process via Edge no longer fails when a data source contains Foreign Keys with references to Database Views. (ticket #86619)
• Jobserver now profiles a scheme even if all the columns in a table contain data of an unsupported type. (ticket #84844)
• The new version of Jobserver mitigates newly raised security vulnerabilities.
• You can now use push-down sampling scan when profiling via Jobserver and using the Databricks driver version 2.6.25 or above. (ticket #92884)
• The S3 synchronization via Jobserver correctly synchronizes S3 assets for which the full name was manually changed in Collibra. (ticket #91640)
• You can now perform a Test Connection via Jobserver for a Parquet driver file on Azure Data Lake Storage (ADLS) with the includeSubdirectories connection property enabled. (ticket #87961)
• You can now use partial scan when profiling via Edge and using the Databricks driver version 2.6.25 or above.
• Increased stability of the database registration job via Edge by closing the JDBC connection immediately after reading the data. (ticket #90915)
• Fixed an issue where profiling via Edge was reported as failed if there were one or more empty schemas in the database. (ticket #90918)
• The 'Data Entity contains / is part of Data Attribute' relation is again available for Power BI Table assets. (ticket #89594, 89624, 90101, 90197, 92696)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• When creating a technical lineage for BigQuery, stitched elements are now correctly identified by “Catalog & Technical Lineage" on the Stitching tab page. (ticket #89558)
• When attempting to integrate Power BI with invalid Power BI credentials, the lineage harvester log file now provides a more helpful error message.
• When integrating Power BI via the lineage harvester, API call results are now streamed directly into JSON files, instead of being stored in memory, which reduces the chances of out-of-memory errors. (ticket #93502)

• PowerBI dataflows without names that are returned by Power BI API are now skipped during the scanning phase.

Data Governance

• While editing the edges of a node in the diagram view editor, you can once again filter by business qualifier. (ticket #84377)
• If you filter a view based on the Created by or Last modified by fields, assets created or modified by a deleted user now appear correctly.
• Bar chart widgets now trim long community names instead of shrinking the chart area.
• If you resize a column in an Activities table in the Collibra Settings and then search the column, the width adjustment is now retained and you can once again wrap the text in the cells of that column. (ticket #81644)
• While editing the edges of a node in the diagram view editor, you can now use keywords from the head and tail as well as the role and corole in the Relation Type field. (ticket #88313)
• The asset counter in the lower right corner of a filtered view with more than 10.000 assets now shows the correct number of assets in the table when clicked. (ticket #88791, 89367)
• The asset counter in the lower right corner of a filtered view with more than 10.000 assets now shows the correct number of assets in the table when clicked. (ticket #88791, 89367)
• Fixed an issue which could prevent you from creating issues. (ticket #87994)
• If you move a domain to another community, you now see an entry on the History tab page of that domain, the former parent community and the new parent community. (ticket #91456)
• After editing an asset, you no longer have to refresh the asset page to see new entries on the History tab page.
• You can once again sort the Domain Types table. (ticket #86049)
• If you are on a community page and you create a child community or domain, the organization tree of the community is now updated without refreshing the page.
• Using the Global Create, you can no longer create assets of a specific type in domains of any type if the asset type's assignment doesn't allow you to.
• Fixed an issue where an asset type page didn't load if the same domain type was assigned more than once. (ticket #80197)
• You can once again generate a new user password if the maximum length is set to less than 16.
• Your account is now correctly locked after the set number of unsuccessful sign-in attempts if the lock-out duration is disabled.
• The exported file of the Users table now uses a comma as delimiter. (ticket #73071)
• If you delete a community or domain that has shared views or filters, you no longer need a global role with the Manage shared Views, Dashboard and Search Filter global permission. Note that you still need a resource role with the Community > Remove or Domain > Remove resource permission. (ticket #86525)
• If you set a context path for your environment, the URLs of the DGC settings are now correct. (ticket #86434, 88886)

Miscellaneous

• 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)

• You now have an Edge Jobs dashboard that gives you pertinent information about your Edge sites and all of their jobs. From this dashboard, you can cancel jobs in real time or download the output files of jobs, which contain log files such as log files for example to troubleshoot a failed job.
• The Collibra sampling feature has been enhanced and can now support the use of sample data via Edge. Users with the required permissions can request to see sample data for a data source registered via Edge. On request, the sample data is collected and made available to the user. The new Collibra sampling feature is a preview feature that needs to be activated.
• Collibra is proud to launch a brand new feature, Data Marketplace. Data Marketplace allows for an easy search experience through Data Catalog assets in Collibra Platform.
  Data Marketplace is a feature in preview that needs to be activated. The following settings are available in Collibra Console:
  • Data Marketplace
  • Search over relations
  • Consistency for custom facets and Search over relations

Hotfixes

Collibra 2022.08.1

• Data Quality & Observability Classic customers can now download the Edge installer from the Data Quality & Observability Classic Edge management page.
• If you click a link to a view, the correct view is now displayed, instead of the view that you last visited. (ticket #94044, 94108, 94173, 94252, 94277, 94396)
• Fixed the issue with S3 synchronization via Jobserver that was caused by connection issues on HTTP level. (ticket #90141, 91640)
• The PostgreSQL JDBC Driver is upgraded to version 42.4.1. (ticket #94706)

Collibra 2022.08.2

• Fixed an issue with SSO that caused Collibra Console to crash because of a memory leak. (ticket #93202, 93244, 93273, 93378, 93442, 93539, 93868, 94056, 94166, 94215, 94545, 94596, 94701, 94768, 95607, 95812, 96417)

Collibra 2022.08.3

• Apache Commons Text has been upgraded to version 1.10.