2022.09

• Release information
• Highlights
• Enhancements
• Fixes
• Beta features

Release information

• Release date of 2022.09.0: September 11, 2022
  • Upgrade non-production environments: September 11, 2022
  • Upgrade production environments: October 2, 2022
• Relevant Jobserver version: 2022.08.1-56

Highlights

• Previously, when you created a technical lineage for Power BI, SQL Server Reporting Services (SSRS) or Power BI Report Server (PBRS), 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, SSRS or PBRS. We introduced this enhancement for Tableau and Looker in Collibra 2022.07.

Enhancements

Data Governance

• If your administrator specifies a new password or generates a new password automatically, you no longer receive an email containing your password. Instead, your administrator should provide you with the password.

Miscellaneous

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

Fixes

Data Catalog

• You can now register an Oracle data source with a service name that contains @ # $ _ . or - via Edge. (ticket #90951)
• The Data Classification tab now shows all data classes, including the data classes created by users who are deleted. (ticket #87166)
• If a network issue occurs while registering a JDBC data source via Jobserver, Collibra again retries repeatable network requests. (ticket #87158)
• Fixed the issue with S3 synchronization via Jobserver that was caused by connection issues on HTTP level. (ticket #90141, 91640)

Data Lineage and BI integrations

• When you integrate Tableau:
  • You can now ingest subprojects for which you have permission to ingest, even if you don’t have permission to ingest the parent projects. (ticket #90508)
  • If you use domain mapping, subprojects are now ingested in the domains of their parent projects. (ticket #93071)
  • For every Tableau Workbook that you have permission to ingest, all Tableau Dashboards in the Workbooks are now correctly shown in the technical lineage graph. If you do not have permission on the Workbook or Dashboard level, the metadata of these data objects is not ingested. (tickets #90508, 91225)
• When you integrate SQL Server Reporting Services (SSRS) or Power BI Report Server (PBRS) data sources, relations between SSRS assets are again correctly created and shown in the technical lineage graph. (ticket #88100)
• When you integrate Power BI:
  • The descriptions of Data Set Tables and Data Set Columns in Power BI are now harvested. (ticket #92736)
  • The lineage harvester is now more resilient to OutOfMemory errors. (tickets #93502, 94681)
• When you integrate an Oracle data source, the value of the "databaseNames" property in your lineage harvester configuration file must be either the Oracle SID or service name, depending on whether you set the "connectAsServiceName" property to "true" or "false". This means that the database in the technical lineage will have the name of the Oracle SID or service name. However, if the database asset in Data Catalog reflects the true name of the database, stitching will break. To resolve this issue and preserve stitching, you need to rename the database asset in Data Catalog to match the value you put for the "databaseNames" property. This is a known issue that we will fix in a future release.
• When integrating Snowflake data sources, the value of the collibraSystemName property in the lineage harvesterconfiguration file is now correctly taken into account. (ticket #94314)
• The PostgreSQL JDBC Driver is upgraded to version 42.4.1. (ticket #94706)
• The Collibra Data Lineage service instances now support the WITH UR clause when integration Oracle data sources. (ticket #89528)
• The Collibra Data Lineage service instances now benefit from the following parsing enhancements when integrating Snowflake data sources:
  • Support for the COLLATE keyword.
  • Support for EXTERNAL TABLE syntax.
  (ticket #92196)
• The Add to Data Basket button is again available for Power BI Report (or children) assets. (ticket #89409, 91978)
• Informatica PowerCenter scanner now stitches correctly for mapping overrides for ETL targets. Previously, it stitched to the wrong assets in Data Catalog.
• Fixed an issue that was resulting in a processing error when a column referenced in an ORDER BY clause references a repeated column in the SELECT column list. (ticket #92330)

Data Governance

• You now only see the Actions menu on a community or domain page if you can do at least one of the listed actions.
• You no longer see code if you scroll down on certain dashboards. (ticket #94298)
• When importing assets or complex relations, testing the import no longer fails if the user interface language is not set to English. (ticket #91500)
• The Output module once again returns responsibilities for non-administrator users if Enable joins for view permission filtering is enabled. (ticket #90057, 90829, 91185)
• The order of widgets on a dashboard now stays the same after refreshing the page. (ticket #84353)
• If you switch between single-path and multi-path hierarchy in an asset table, you no longer have to refresh the page to see the new hierarchy.
• If a community or domain for which you don't have view permissions is used in a criterion of an asset filter, then you cannot edit the filter and don't see the criterion.
• Fixed an issue where the title was missing from the attribute dialog box when adding an attribute as a characteristic on an asset page. (ticket #94997).

Diagrams

• The preview pane in a diagram once again shows the correct ratings of the selected asset. (ticket #89769)
• If you open another node from a diagram using Start here and select the current diagram view, Collibra no longer stays on the current asset but opens the diagram starting from the selected node. (ticket #90567, 92496, 94901)
• If you add an edge to a node in a diagram, the value that you select in the Relation Type field (for example, Technology Asset is system of record for Business Asset) no longer disappears. (ticket #88544)

Collibra Console

• 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)
• Fixed an issue that prevented new users who were created in Collibra Console from changing their password via the link within their initial confirmation email. (tickets #90311, 90831, 91223, 91348)

Miscellaneous

• If you switch between views on the Assets tab page of a community, the view ID in the URL is now updated correctly.

Data Marketplace

• If Analytics are enabled in your Collibra environment, the Data Marketplace landing page shows Popular Data and Recommended Data, instead of Recent Searches and What's New. See The Data Marketplace landing page.
• Fixed an issue where Tags were incorrectly mentioned to match the search in the Search results.
• Fixed an issue where only the first 50 statuses were available for selection in the Data Marketplace scope.
• You can select all asset types via the Select all checkbox in the Data Marketplace scope.
• The Search field is now cleared when search suggestions are enabled and you click the X icon.
• The Primary Action label now shows the start label of the selected workflow definition instead of the name attribute of the workflow.

2022.08

• Release information
• Highlights
• Metamodel changes
• New features
• Enhancements
• Fixes
• Beta features
• Patches

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

• You can now filter on the Tableau project level. This is a beta feature.
• 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.
• 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.
• 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 packaged data classes for Automatic Data Classification were enhanced:
  • The "SSN" class performance was improved.
  • The "Phone number" class now allows dots (.) as separators.
  • The "IP address" now allows leading zeros (0).
  • The "Email" class now allows for IP addresses in addition to domain names.
  • A new class "Canadian Postal Code" was added.

• 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

• 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.
• 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".
• 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.
• 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.
• 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.

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• You can now prepare a Looker <source ID> configuration file, to specify which Looker Folders you want to ingest in Collibra.
• When you specify the Power BI workspaces for ingestion, the filters are not case sensitive now.
• 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.
• 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 integrating Power BI, you can now include the optional found_schema property in the databaseMapping section of your Power BI <source ID> file, to map a schema that is used in Power BI to a Schema asset in Collibra, thereby preserving stitching.
• 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.
• 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.
• 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.
• 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.
• The lineage harvester log file now identifies whether you are using Tableau Online or Tableau Server, and the version of your Tableau environment.
• Tableau Site asset pages now show the relations to both projects and subprojects.

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)
• You can now create and edit complex relations in fewer steps.
• 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.
• 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.
• Deleting domains containing assets with complex relations is now faster. (ticket #76864, 77356, 77550, 81203, 82723, 83977)
• Assigning a responsibility to a group with a lot of users is now faster.

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 Data Intelligence Cloud environment no longer fails if your webpage address does not contain the Tableau site or workbook name. (ticket #89169)

Data Catalog

• 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)
• You can now use partial scan when profiling via Edge and using the Databricks driver version 2.6.25 or above.
• 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)
• The S3 synchronization via Jobserver correctly synchronizes S3 assets for which the full name was manually changed in Collibra. (ticket #91640)
• The new version of Jobserver mitigates newly raised security vulnerabilities.
• The database registration process via Edge now returns the correct schema name for databases that contain only one schema. (ticket #81495
• The database registration process via Edge no longer fails when a data source contains Foreign Keys with references to Database Views. (ticket #86619)
• The 'Data Entity contains / is part of Data Attribute' relation is again available for Power BI Table assets. (ticket #89594, 89624, 90101, 90197, 92696)
• Jobserver now profiles a scheme even if all the columns in a table contain data of an unsupported type. (ticket #84844)
• Increased stability of the database registration job via Edge by closing the JDBC connection immediately after reading the data. (ticket #90915)
• 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.
• 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)
• Fixed an issue where profiling via Edge was reported as failed if there were one or more empty schemas in the database. (ticket #90918)
• Catalog asset pages now load faster even if the Catalog Experience setting is disabled. (ticket #71958, 76040)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

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

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

Data Governance

• Your account is now correctly locked after the set number of unsuccessful sign-in attempts if the lock-out duration is disabled.
• You can once again sort the Domain Types table. (ticket #86049)
• You can once again generate a new user password if the maximum length is set to less than 16.
• While editing the edges of a node in the diagram view editor, you can once again filter by business qualifier. (ticket #84377)
• 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)
• 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.
• The exported file of the Users table now uses a comma as delimiter. (ticket #73071)
• 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)
• If you set a context path for your environment, the URLs of the DGC settings are now correct. (ticket #86434, 88886)
• 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)
• 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)
• 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.
• 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 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.
• Fixed an issue which could prevent you from creating issues. (ticket #87994)
• Fixed an issue where an asset type page didn't load if the same domain type was assigned more than once. (ticket #80197)
• Bar chart widgets now trim long community names instead of shrinking the chart area.
• After editing an asset, you no longer have to refresh the asset page to see new entries on the History tab page.

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 Site 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 beta 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 Data Intelligence Cloud.
  Data Marketplace is a beta feature 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

Patches

Patch 1

• Data Quality customers can now download the Edge installer from the Data Quality 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)

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

2022.07

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

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

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

Enhancements

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• 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.
• 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.
• 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)
• Collibra Data Lineage now supports assets with UUIDs.

Fixes

Data Catalog

• 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)
• 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)
• 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)
• Table and column assets in domains with restricted View permissions can now be profiled via Edge. (ticket #88149)
• 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)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• When the lineage harvester fetches an access key for a data source, only active records are now fetched. Inactive records are ignored. (ticket #88388)
• 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 lineage harvester now retries to get a batch status if the first HTTP call failed due to a network error.
• The lineage harvester is more resilient against authorization expiration when ingesting Looker metadata. (ticket #87429)
• The Collibra Data Lineage servers now support parsing of single-table INSERT OVERWRITE INTO statements when ingesting Snowflake metadata. (ticket #89228)
• The Collibra Data Lineage servers now skip Excel SQL statements, as they are not supported. (ticket #88424)
• 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)
• Lineage harvester error message MSG-LIN-3005, “Fiber error on Snowflake”, is now raised and included in the technical lineage logs. (ticket #86009)
• Fixed an issue with Power BI Table external entity IDs. Power BI Tables are now shown in the technical lineage. (ticket #89542)
• Fixed an issue that was resulting in the No asset matches the specified criteria error.
• 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)
• Fixed an issue that resulted in a processing error when integrating MicroStrategy. (ticket #90048)
• Collibra Data Lineage now supports worklets contained in other worklets with the same name, when ingesting metadata from Informatica Intelligent Cloud Services. (ticket #90234)
• Collibra Data Lineage now supports Row Access Policy in Snowflake CREATE TABLE/VIEW statements. (ticket #88995)
• 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)

Data Governance

• 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)
• 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)
• 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)
• Asset pages now load correctly if the asset name contains special characters. (ticket #89075)

Search

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

Patches

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

2022.06

• Release information
• Highlights
• Enhancements
• Fixes
• Patches

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 Data Intelligence Cloud 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.

• 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.
• When ingesting Power BI, if there are Oracle data sources, the Oracle service name is now used, instead of the database name.
• The UUIDs of Tableau Data Attribute assets are no longer included in the asset name and full name.

Fixes

Data Catalog

• 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)
• The description provided during the XLS or CSV registration is now saved and visible in the Schema Summary and Details pages.
• The Description field in the Summary of asset pages now shows the correct value. (tickets #85164, 83843)
• Technical lineage is now available for Database views. (ticket #84155)
• 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)
• 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)
• Collibra can now profile large Teradata data sources via Edge without numeric overflow error. (ticket #81572)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• When processing Tableau metadata, the Collibra Data Lineage servers no longer replace ">>" by "<}", which was resulting in parsing errors. (ticket #87185)
• When processing Power BI metadata (for Oracle data sources), SQL statements are now in upper case.
• 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)
• 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 TOP.
  • Support for CONNECT BY after WHERE clause.
• 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 potential "show Locks LockManager not specified" error when ingesting HiveQL.
• Fixed an issue that was causing the processing of harvested metadata batches to run without coming to completion. (tickets #86480, 88205)
• Fixed an issue in the script for migrating Tableau assets to the new operating model.
• Fixed an issue in the Collibra Data Lineage servers that was affecting the processing of Tableau Data Attributes.
• Fixed an [SQLITE_ERROR] issue that was breaking the technical lineage when attempting to synchronize a data source. (ticket #85541)
• Changed a web server configuration to support uploading of ZIP files larger than 2 GB. (ticket #87837)

Data Governance

• You no longer get a DataFetchingException error if historical guest users exist in the database and you open the Users page. (ticket #87959, 88857)
• 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)

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.

Security

• Your Collibra session now closes correctly when the session times out. (ticket #65867, 83973, 87289)
• 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.

Patches

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