2022.06

• Release information
• Highlights
• Enhancements
• Fixes

Release information

• Release date of 2022.06.0: June 5, 2022
  • Upgrade non-production environments: June 5, 2022
  • Upgrade production environments: June 26, 2022

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 ingesting Power BI, if there are Oracle data sources, the Oracle service name is now used, instead of the database name.
• When ingesting Power BI metadata, you can now ingest measures and show them in the technical lineage.

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.
• Fixed an issue that was causing the processing of harvested metadata batches to run without coming to completion. (ticket #86480)
• 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)

Data Governance

• With Global create, you can no longer create assets and asset types in communities or domains where it shouldn't be allowed.
• When you add a community or domain at any level in the tree, the table is now correctly updated.
• 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.

Search

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

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.

2022.05

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

Release information

• Release date of 2022.05.0: May 8, 2022
  • Upgrade non-production environments: May 8, 2022
  • Upgrade production environments: May 29, 2022

Highlights

New features

Data Catalog

• xx

Reports and Insights

Collibra for Desktop

Enhancements

Data Catalog

Data Lineage and BI integrations

Data Governance

Assessments

Diagrams

API

Miscellaneous

Fixes

Data Catalog

Data Lineage and BI integrations

Data Governance

Assessments

Diagrams

Workflows

Search

Collibra for Mobile

Security

API

2022.04

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

Release information

• Release date of 2022.04.0: April 10, 2022
  • Upgrade non-production environments: April 10, 2022
  • Upgrade production environments: May 1, 2022

Highlights

New features

Data Catalog

• xx

Reports and Insights

Collibra for Desktop

Enhancements

Data Catalog

Data Lineage and BI integrations

Data Governance

Assessments

Diagrams

API

Miscellaneous

Fixes

Data Catalog

Data Lineage and BI integrations

Data Governance

Assessments

Diagrams

Workflows

Search

Collibra for Mobile

Security

API

2022.03

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

Release information

• Release date of 2022.03.0: March 6, 2022
  • Upgrade non-production environments: March 6, 2022
  • Upgrade production environments: March 27, 2022
• Release date of 2022.03.1: March 25, 2022

Highlights

• You can now show a disclaimer upon successful login. When enabled, you must accept the disclaimer after signing in, or else you are signed out.
  
• The default installation of Edge installs a Kubernetes cluster with Edge deployed on a Linux box that is fully managed by the customer. It is now possible to install Edge on an Edge-dedicated Amazon EKS (Elastic Kubernetes Service) cluster that is fully managed by the customer.
  
• S3 integration on Edge is now generally available.

New features

Collibra for Desktop

• You now see the last updated information on an asset page.
• The Collibra for Desktop settings now includes a tip page with useful hints to use the app.
• Filter suggestions can show asset type, community, or domain filters that are based on the user's browsing history that is stored in Collibra for Desktop.
• Collibra for Desktop can now suggest asset recommendations based on your browsing history.
• An acronym's asset page now shows the description of the corresponding business term.

Collibra Console

• You can now show a disclaimer upon successful login. When enabled, you must accept the disclaimer after signing in, or else you are signed out.

Enhancements

Data Catalog

• You now see a relevant message when running an S3 synchronization and the Jobserver is offline. (ticket #61856)
• You cannot run an S3 ingestion if you have not defined any crawlers.
• The Technical Lineage tab is now available in the asset pages of asset types that support Technical Lineage, even if Catalog experience is disabled.

Data Lineage and BI integrations

• When ingesting Tableau metadata, you can now leave empty the collibraSystemName property in your configuration file, even if the useCollibraSystemName property is set to true.
• When ingesting Power BI metadata, you can now include wildcards in the Power BI <source ID> configuration file.
• The Collibra Data Lineage servers now benefit from the following parsing enhancements when integrating Informatica PowerCenter data sources:
  • Source tables and columns for LOOKUP transformations.
  • SQL overrides.
• Postgres JDBC driver is upgraded to version 42.3.2.
• Hive source now skips harvesting DDL of exclusively locked tables.
• By default, the lineage harvester no longer harvests images. If you want to include images, include the optional excludeImages property in your configuration file and set the value to false.

Data Governance

• You can now add the "Last modified by" field in a view and use it in the filter pane of asset views.
• The Organization page of the Stewardship application can now include inherited responsibilities.
• The Browse pane now only shows the views for which you have view permissions and the relevant global permissions.

API

• You can now use different labels to define multiple columns in the table output query that contain the same data referenced by the "fieldName".
• The console API has a new endpoint to upload backups and process the uploaded file asynchronously. (ticket #76760).
• JSON requests with malformed JSON, such as syntax errors and missing JSON fields, now result in standard API error responses.

Miscellaneous

• Log messages about signing in and out no longer include implementation details and, whenever possible, now contain the user ID instead of the username.

Fixes

Data Catalog

• You can now revalidate assets from the Actions menu in Catalog asset pages, if Catalog experience is enabled. (ticket #77368)
• You can now cancel jobs running via Jobserver without restarting the DGC service. (ticket #77611, 78564, 81416, 82221)
  
• The Add to Data Set button is now again visible in the Physical Data Dictionary domain pages. (ticket #72814, 79646)
• Fixed an issue where schema assets were wrongfully marked as "Missing from source" when synchronizing a single schema via Edge.

Data Lineage and BI integrations

• When you change the domain reference ID in the lineage harvester configuration file, Tableau assets are now successfully deleted from the previous domain and recreated in the new domain.
• When there is no upstream database in Tableau custom SQL, we replace the empty string by "database".
• The lineage harvester now correctly shows the help overview when you run the --help command.
• The Collibra Data Lineage servers now benefit from the following parsing enhancements when integrating Teradata data sources:
  • Numeric literals
  • INSERT INTO x <expressions> SELECT …

  (tickets #82563, 82636, 82637, 82638)

• Relaxed the validation that was causing the ingestion of Looker metadata to fail. (ticket #80308)
• Protobuf upgraded to version 3.19.3. (ticket #81820)
• Protobuf is upgraded to version 3.19.3. (ticket #81820)
• If the asset name is empty, we now use a default name.
• Fixed an issue when ingesting Tableau metadata via lineage harvester that resulted in an UnexpectedConnectionClosureException error.
• Fixed an issue that was causing the ingestion of Looker metadata to fail. (ticket #80154)
• Fixed an issue that was causing a JsonParseError when ingesting Tableau metadata.
• Fixed an issue that resulted in a TableauHarvesterError when ingesting Tableau metadata via the linage harvester. (ticket #82097)
• Fixed a NullPointerException when no column data type is harvested.

Data Governance

• You no longer see the edit icon in table cells on Overview tab pages of domain and community pages if you don't have the permissions to edit the cell content. (ticket #75328)
• You can once again resize columns on community pages. (ticket #78287)
• You can now wrap the text in cells on the Organization page of the Stewardship application.
• The names of domain types and asset types can no longer consist of only spaces.
• Fixed an issue where you couldn't add relation type fields to a view if you used an advanced filter that contained an "OR" operator. (ticket #79342)
• Fixed an issue where new roles didn't appear in the column picker of the Permission pages.
• Fixed an issue where empty relation tables wrongly appeared on asset pages. (ticket #74634)
• Fixed an issue in the Complex Relation Type field when importing complex relations. (ticket #75736)
• Domains whose name contain an underscore now correctly appear in the Domain field of the Create Asset dialog box.

Workflows

• The purge job now correctly clears out the workflow history. (ticket #70514)
• Inserting an image into a workflow form no longer causes an error or prevents the image from being stored. You can paste images of up to 2 MB in PNG, JPG, JPEG, or GIF format. (ticket #59568, 75092)

Collibra Console

• Upgrading Collibra no longer resets the option to show the API documentation menu item to admins only. (ticket #74974)

Security

• The current session endpoint of the REST API v2 now includes the associated CSRF token when applicable, and, optionally, the user information for the session.

API

• You can now use the API to delete a domain if it has a view. (ticket #77202)
• The REST Import API now interprets correctly column values in a CSV file where the multivalue quote is "|". (ticket #71853)
• The Java User API now returns the correct exception if a user is not found when searching on username.
• The batches of the Relations REST Core API method no longer have overlapping content.
• The batches of the ComplexRelations REST Core API no longer have overlapping content. (ticket #80323)
• Fixed an issue that led to inconsistent results in the output module. (ticket #73570, 76795)

Miscellaneous

• If you have Collibra open in multiple tabs, your session now times out correctly. (ticket #65867)

Patches

Patch 1

• Fixed an issue where a CSRF token was missing from the response when no cookies were set for the auth/session API. (ticket #83781, 83808, 83822, 83862, 83892, 83920, 84009, 84054, 84164, 84182, 84455, 84767)
• Azul Zulu JRE (Java Runtime Environment) is updated to version 8.0.322. Jobserver has also been upgraded to version 2022.2.3-58 to support this JRE version. (ticket #83442)
• You can again use the 'BETWEEN' filter in the Output Module. (ticket #83068, 83202)
• The Argo-cd redis for Edge is updated to remediate vulnerabilities. (ticket #83135)

Edge capability patch 1

• jdbc profiling capability: The profiling job now waits 20 minutes for a response when submitting profiling results to Catalog, instead of waiting indefinitely. After 20 minutes, the profiling job starts to process the next table.

• Catalog jdbc ingestion capability: If you receive an out of memory error when you synchronize or profile a data source via Edge, you can now retrieve a diagnostics log file to investigate the issue in detail.

2022.02

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

Release information

• Release date of 2022.02.0: February 6, 2022
  • Upgrade non-production environments: February 6, 2022
  • Upgrade production environments: February 27, 2022
• Release date of 2022.02.1: February 27, 2022
• Release date of 2022.02.2: March 17, 2022
• Release date of 2022.02.3: March 25, 2022

Highlights

• You can now use a browser extension to easily access Tableau or PowerBI Dashboard metadata.
• You can now ingest Tableau metadata via the lineage harvester. This allows you to ingest embedded data sources and allows for custom SQL parsing, automatic stitching and much more.
• When profiling on Edge, you can now choose which synchronized schemas are to be profiled. See Configure the profiling and classification options via Edge.
• The following Catalog connectors are now certified for Edge:
  • Sybase
  • SQL Server
  • Couchbase
  • Cloudant
  • Azure Synapse
• iOS 11 is no longer supported for Collibra for Mobile 1.5.2 and newer.

New features

Data Catalog

• You can now use partial scan to profile most columns of Impala data sources via Jobserver, except for those in views, Kudu tables, and HBase tables.
• You can now use partial scan to profile Google BigQuery data sources via Jobserver.
• When profiling on Edge, you can now choose which synchronized schemas are to be profiled. See Configure the profiling and classification options via Edge.
• The following Catalog connectors are now certified for Edge:
  • Sybase
  • SQL Server
  • Couchbase
  • Cloudant
  • Azure Synapse

Data Governance

• You can now use views on the Organization page of the Stewardship application.
• The Scope page is now redesigned to make it more user friendly. For example, you can now easily see which domains and communities belong to which scope, and you also see a warning if a community or domain is in multiple scopes.

Collibra for Desktop

• The following settings can now only be defined in Collibra Console and no longer in the Collibra for Desktop settings:
  • Default filter
  • Reporting
• When the user settings are disabled, the keyboard shortcut is no longer visible in the user settings.
• Via the unattended installation, you can now only configure the environment URL, session timeout and initial message. All other options can only be configured via Collibra Console.
• You can now change the colors and logo of Collibra for Desktop to be more in line with your company's brand.

Collibra for Mobile

• iOS 11 is no longer supported for Collibra for Mobile 1.5.2 and newer.

Enhancements

Data Catalog

• You can configure the maximum number of characters to take into account per cell when profiling via Edge, by changing the Maximum value length field. See Configure data profiling behavior.
• The Jobserver component has been updated and requires an upgrade. See Compatibility between Jobserver and Collibra.

Data Lineage and BI integrations

• When ingesting metadata from Tableau Server 2021.3 or newer, Tableau workbooks in Personal Space are not ingested. For complete information on Personal Space in Tableau, see the Tableau documentation. (tickets #77501, 80903)
• Upgraded JDBC drivers for MySQL, PostgreSQL, Teradata, Snowflake, HiveQL, Spark SQL and Microsoft SQL Server data sources. Discontinued support for Active directory authentication for Azure data sources. (Ticket #73867)
• The new Tableau integration via lineage harvester supports the Tableau Explorer role.
• The lineage harvester includes mitigations for the following log4j vulnerabilities:
  • CVE-2021-44228 (December 10, 2021)
  • CVE-2021-45046 (December 14, 2021)
  • CVE-2021-45105 (December 18, 2021)
• Netty libraries are upgraded to version 4.1.72. (ticket #79732)
• Hive JDBC driver is upgraded to AmazonHiveJDBC42-2.6.17.1020.

Data Governance

• If moving a domain or community causes a conflict of scopes, the moved domain and community is now removed from its original scope.

Assessments

• URLs for conducting assessments are simplified, to facilitate the integration of assessments in dashboards and workflows.
  
  Note When implementing this change, we also adjusted the terminology used in the URL to reflect terminology used in the Assessments app. This could result in broken links if you use the URLs outside of the Assessments app. We encourage you to verify such links if you use them, for example, in dashboards or workflows.

Collibra for Mobile

• The Expo SDK is upgraded to version 43 to fully support iOS 15.
• General performance and stability improvements.

Fixes

Data Catalog

• When profiling on Edge, Collibra now takes a configurable maximum number of characters into account per cell. The default maximum is 1,000. This allows to profile cells containing long values, for example cells of the Long data type in Oracle. (ticket #73469)
• If you have the Technical Lineage global permission, you can now see the Technical Lineage tab on the Database View asset page. (ticket #70049)

Data Lineage and BI integrations

• When viewing transformations in a technical lineage, you can again right-click on nodes that have duplicate names, to open the context menu. (ticket #77458)
• When using a parameter file during the ingestion of metadata from Informatica PowerCenter data sources, parameter names are now correctly replaced by the values in the source table name override. (tickets #75833, 78084)
• When processing a report file, the SSRS scanner now creates an SSRS Data Model asset in Collibra Data Intelligence Cloud for each dataset of the report. SSRS Columns related to those SSRS Data Model assets are now also created in Collibra. (ticket #78930)
• When metadata from Snowflake data sources are analyzed, schema names are no longer wrapped in double-quotes. (ticket #77213)
• When ingesting metadata from Microsoft SQL Server data sources, the dash character "-" in database names no longer causes ingestion to fail. (ticket #75860)
• The lineage harvester now renews the Looker API token if harvesting takes longer than one hour, to avoid an HTTP 401 Unauthorized error.
• The lineage harvester now correctly shows the help overview when you run the --help command.
• The Collibra Data Lineage servers now benefit from the following parsing enhancements for data sources of the following types:
  • SQL Server Integration Services: components of type "Microsoft.ScriptComponentHost", which is a subtype of the "Microsoft.ManagedComponentHost". (ticket #76036)
  • Redshift:
    • Optional enclosing brackets [] for table references. (ticket #77184)
    • DELETE queries that have WITH statements. (ticket #74380)
  • Oracle:
    • ON OVERFLOW clause of LISTAGG function. (ticket #73709)
    • ENCRYPT algorithm in CREATE TABLE column definition.
  • Microsoft SQL Server: all variants of hexadecimal literals. (ticket #78078)
  • BigQuery: PARTITION BY clause in CREATE TABLE statements. (ticket #77044)
• Support for Oracle package specifications split into multiple source files (e.g. package definition in one source file and package body in another source file). (ticket #74529)
• Support added for ALTER TABLE RENAME TO statement in Postgres. (ticket #75894)
• If you change the domain reference ID in the lineage harvester configuration file, Tableau assets are now successfully deleted from the previous domain and recreated in the new domain.
• Fixed the computational inefficiency in the SQL scanner in the case of multiple nested subSELECTs with wildcards. (ticket #76637)
• Fixed a NullPointerException when no column data type is harvested.

Data Governance

• You can now create a filter based on asset types of all subcommunities in the filter pane of a root community page. (ticket #71357, 76104)
• The References tab page of asset pages now show references to assets with parentheses in their names. (ticket #67907)
• The popup that appears if you point to a hyperlink in an attribute now shows long breadcrumbs correctly. (ticket #76626)
• Log messages about signing in and out no longer include implementation details and, whenever possible, now contain the user ID instead of the username.
• If you open an asset page from a relation table, the asset page now opens at the start of the page. (ticket #67587)
• Fixed an issue where the Task Duration widget in a dashboard kept spinning indefinitely. (ticket #71492)
• Fixed an issue where the Automatic Hyperlinking feature sometimes created hyperlinks to assets whose type was excluded in the configuration.
• Fixed an issue that occurred when editing cells in the Group column of the users table. (ticket #74109)
• Fixed an issue that caused the import feature to fail if you imported assets with relations. (ticket #79963, 79989, 79995, 80010, 80011, 80046, 80077, 80088, 80110, 80145, 80148, 80151, 80153, 80171, 80182, 80193, 80196, 80204, 80214, 80229, 80238, 80288, 80300, 80307, 80318, 80321, 80341, 80360)
• Fixed an issue in the error message that appears if you import complex relations with too many legs. (ticket #73694)
• Fixed an issue in the Complex Relation Type field when importing complex relations. (ticket #75736)

Assessments

• Assessment templates with very long names no longer cause the UI to malfunction.

Workflows

• Completing a workflow task in the task bar no longer causes a task bar refresh error in some cases.

Collibra for Desktop

• Date and time is now correctly shown in Collibra for Desktop. (ticket #76283)
• Collibra for Desktop now correctly shows diagram pictures that are public or shared with the Everyone group. (ticket #73212, 74810)

API

• The typeId parameter of the GET/Assets is now deprecated in favor of typeIds. (ticket #75809)
• The REST Import API documentation now mentions that the finalization method requires at least one of the optional parameters to be specified.
• JSON requests with malformed JSON, such as syntax errors and missing JSON fields, now result in standard API error responses.
• Fixed an error in the response schema for the POST /assetTypes/bulk and POST /attributeTypes/bulk methods of the REST Core API v2. (ticket #74894)

Patches

Patch 1

• You can once again open communities in a new tab page from a link. (ticket #80081, 81342)
• Search fields in dialog boxes of workflows now correctly filter on asset types and show all relevant assets. (ticket #76946, 80426)
• Log4j is upgraded to version 2.17.1. For technical information regarding the Log4j 2.17.1 release, please consult the Log4j release notes.

Patch 2

• Jobserver has been upgraded to a higher version (2022.02.2-47) to improve security. We recommend you to install this new Jobserver version without delay to remediate the vulnerabilities.

Patch 3

• The Browse pane no longer contains domains and communities for which you don't have view permissions. (ticket #82447, 82986, 83313, 83393, 83470)
• You can again use the 'BETWEEN 'filter in the Output Module. (ticket #83068, 83202)
• Azul Zulu JRE (Java Runtime Environment) is updated to version 8.0.322. Jobserver has also been upgraded to version 2022.2.3-58 to support this JRE version. (ticket #83442)
• The Postgres driver is upgraded to org.postgresql 42.3.3.

Lineage harvester patch 1

• The lineage harvester now correctly shows the help overview when you run the --help command.
• Fixed a NullPointerException when no column data type is harvested.
• When you change the domain reference ID in the lineage harvester configuration file, Tableau assets are now successfully deleted from the previous domain and recreated in the new domain.

Lineage harvester patch 2

• Fixed an issue that was causing incomplete technical lineage and stitching issues when using custom SQL in Tableau.
• Fixed an issue that resulted in a TableauHarvesterError when ingesting Tableau metadata via the linage harvester. (ticket #82097)

Edge capability patch 1

• jdbc profiling capability: The profiling job now waits 20 minutes for a response when submitting profiling results to Catalog, instead of waiting indefinitely. After 20 minutes, the profiling job starts to process the next table.

• Catalog jdbc ingestion capability: If you receive an out of memory error when you synchronize or profile a data source via Edge, you can now retrieve a diagnostics log file to investigate the issue in detail.