Collibra Data Intelligence Cloud

The content of this section is only available for Collibra Data Intelligence Cloud. For the release notes of on-premises Collibra Data Governance Center, see Collibra Data Governance Center On-Premises.

Tip Please upgrade any on-premises Jobserver that interacts with Collibra 2022.07 to version 2022.5.1-67.

Note Some items included in this release may require an additional cost. Please contact your Collibra representative or Customer Success Manager with any questions.

Archive section
Only show release notes for FedRAMP-certified features

2022.07

Release information

  • Release date of 2022.07.0: July 10, 2022
    • Upgrade non-production environments: July 10, 2022
    • Upgrade production environments: July 31, 2022

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.

Data Governance

  • If you mention a user in a comment, the selector now also shows the user's email address.

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 #89830, 90085)

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)

Edge

Note Edge is a cloud-only feature.

  • When you navigate to another page in the Job Status table in Edge, the first page no longer disappears.
  • Fixed an issue where binary secret files, for example a keystore for connections, were not correctly encrypted. (ticket #75375, 76571, 77382)

Search

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

2022.06

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

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.

Edge

Note Edge is a cloud-only feature.

  • When you specify an invalid region name in the AWS region restriction console configuration, an error is now reflected in the logs.
  • Host exposure to pods is limited to the OpenTelemetry and DataDog agents. These agents have read-only access to the host file system which is required to read the logs from the pods.

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.

Edge

Note Edge is a cloud-only feature.

  • The lineage harvester on Edge now logs all errors from the load source phase.
  • At the start of an S3 synchronization process, the search for previous AWS Glue databases now respects the AWS region restriction rules.

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)

2022.05

Release information

  • Release date of 2022.05.0: May 8, 2022
    • Upgrade non-production environments: May 8, 2022
    • Upgrade production environments: May 29, 2022
  • Release date of 2022.05.1
    • Upgrade non-production environments: May 22, 2022
    • Upgrade production environments: May 29, 2022
  • Release date of 2022.05.2: June 5, 2022
  • Release date of 2022.05.3: June 24, 2022

Highlights

  • You can now use a browser extension to easily access Collibra data anywhere. Special experience foreseen for Tableau or PowerBI Dashboard metadata.
  • You can now integrate Power BI in Data Catalog via the lineage harvester, meaning you no longer need to use the Power BI harvester. Additional benefits include the following:
    • Support for Power BI Data Flows.
    • Descriptions of Power BI Reports.
    • Statuses of Power BI Workspaces.
    • Filtering and domain mapping.

    Note The new Power BI integration method is specifically for new integrations. For those who have been ingesting Power BI via the Power BI harvester, we will soon release a migration script.

  • The REST Import API v2 now supports importing responsibilities for communities, domains and assets.
  • Collibra Data Lineage now supports the following BI integrations:
  • Azul Zulu JRE (Java Runtime Environment) is updated to version 11.0.14.1.

New features

Data Catalog

  • A new REST API, REST Catalog Database Registration API, is available.
    This API allows you to register data sources via Edge and synchronize the metadata of these data sources outside of the UI.

Edge

  • The Job Status tab in Edge shows all the job capabilities running on all Edge sites and other important task information.

Search

  • When you rebuild the search index for your Collibra environment, the Output Module is now used to fetch the data. This new, default method greatly improves performance during index runtime. There are no changes to the search index configuration settings or the means by which you reindex your environment. If considered necessary, you can roll back to the old indexing method, via Collibra Console.

Browser Extension

  • You can now use a browser extension to easily access Collibra data anywhere. Special experience foreseen for Tableau or PowerBI Dashboard metadata.
  • You can now add web domains for the Browser Extension in Collibra Console.
    If a domain exists in both Console and in the Browser Extension settings, the settings from Console takes precedence. Domains that are added via Console cannot be edited or removed in the Browser Extension settings.

Enhancements

Data Catalog

  • The percentage shown in the main menu Activities list now shows the actual progress of the activity for a Database Profiling via Edge job.

Data Lineage and BI integrations

  • You can now use token-based authentication when creating a technical lineage for Matillion.
    Warning This enhancement is not backwards compatible.
    • You must update your lineage harvester configuration file.
    • If you use the lineage harvester 2022.05, you can no longer use the pwd.conf file with an older harvester.
  • You can now use the lineage harvester and a new migration script, to migrate your Tableau assets to the new Tableau operating model.
  • The State attribute type is now part of the global assignment of the Power BI Workspace asset type.
  • The new Power BI Data Flow asset type now accommodates the ingestion of Power BI dataflows.
  • The asset types Power BI KPI and Power BI Parameter are removed. SQL Server Reporting Services and Power BI Report Server now use the same asset types.
  • If using a Tableau <source ID> configuration file:
    • You can now use wildcards throughout the file.
    • The hostName and connectorUrl properties are no longer case-sensitive.
  • Looker Dashboard asset pages now include a URL to the dashboard in Looker, as a clickable link.
  • If you set the useCollibraSystemName property to "true" in your lineage harvester configuration file, but don't define the system name in the Tableau <source ID> configuration file, the system name in the Tableau technical lineage now shows DEFAULT as the system name.
  • When integrating Informatica Intelligent Cloud Services, Collibra Data Lineage now shows more meaningful error messages when taskflows cannot be processed. For more information and troubleshooting suggestions, see error codes MSG-LIN-19001 and MSG-LIN-19002 in the Documentation Center.
  • The Collibra Data Lineage servers now assign names to SQL queries that are identified by BI and ETL scanners.
  • lineage harvester 2022.05 includes an internal format change to the password manager pwd.conf file.
    Warning This means that if you use the lineage harvester 2022.05, you can no longer use the pwd.conf file with an older harvester.

Data Governance

  • Searching for users in user selection fields now also shows corresponding email addresses.
  • Searching for users in user selection fields now also show email addresses next to the first and last name so that users with the same first and last name can be distinguished.
  • If you import a CMA file using the Migration feature, you now see an overview of the changes before the actual import.
  • All user selection fields in dialog boxes and tables now show the users' first name, the last name and email address.

Edge

  • To monitor metrics, Open Telemetry (OTEL) replaces SignalFX.
  • Spring Boot on Edge is upgraded to 2.6.6 to fix a security vulnerability. (ticket #85853)
  • CDATA logs are now available in the Job Summary table.

Browser Extension

  • When you add a current web page to the domains in the Browser Extension configuration, the Browser Extension automatically starts on that page without refreshing.
  • A loader spinner appears when a search request takes longer than expected.

Collibra Console

  • You no longer have to restart Collibra after changing the hyperlinking configuration.
  • You can now enable or disable the ability to import responsibilities at asset level via the Import API with a new option in the Import configuration section. This option is disabled by default to ensure minimum impact on system performance.

Security

  • You can now configure how long the link that is sent when you reset a password remains valid. The link that is sent when you request a password reset now becomes invalid if you request a new password reset. By default this time is set to 1h with a possible maximum of 24h.
  • You can now configure a period during which you cannot sign in after entering a wrong password too many times. By default, new environments only allow for 3 attempts before a time delay of 5 minutes is triggered.
  • The default password policy for new environments now requires strong passwords. For existing environments, we recommend to review the password policy configuration.
  • If you try to reset your password but you enter a password that is too weak or the password confirmation is wrong, the fields are now cleared.

API

  • The REST Import API v2 now supports importing responsibilities for communities, domains and assets.
  • In the GET /assets REST API method, the statusId argument is deprecated, use the argument statusIds from now on.
  • Additional capability metrics are added to the Edge GraphQL API which allow you to verify if capabilities are used, correctly functioning or failing regularly.

Miscellaneous

  • The performance of bulk deleting assets with complex relations has improved.
  • Signing in via LDAP is now faster. (ticket #79896, 83727)

Fixes

Data Catalog

  • To avoid out-of-memory issues, you can now use the 'Data set threshold' setting to limit the number of elements used in the Data Set recommender model training. (ticket #77440, 79644)
  • The Target Domain drop-down list now always shows up to 100 applicable target domains. To narrow the selection, you can start typing the name of the domain. (ticket #81360)
  • Fixed an issue in Jobserver Job management that could prevent a job from completing. (ticket #83630)

Data Lineage and BI integrations

  • You can now use the optional concurrencyLevel property in the lineage harvester configuration file, to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. (tickets #82323, 85617)
  • When ingesting Tableau, automatic stitching is again creating the relation type "Data Element sources / targets Data Element" between Tableau Data Attribute assets and BigQuery Column assets. (ticket #86149)
  • When harvesting IBM InfoSphere DataStage data sources, all inside SQL statements are now analyzed.
  • When harvesting BigQuery metadata, materialized views are now harvested. (ticket # 84273)
  • The PostgreSQL JDBC driver is now upgraded from 42.3.2 to 42.3.3.
  • The lineage harvester no longer hangs when harvesting metadata from certain data sources.
  • The lineage harvester automatically refreshes Tableau tokens. (tickets #82323, 85617)
  • The Collibra Data Lineage servers now benefit from the following parsing enhancements when integrating Teradata data sources (ticket #84666):
    • Support for the DECLARE CURSOR statement in its dynamic SQL form.
    • Support for MINUS ALL and plain MINUS.
    • Support for INCLUDE_NULLS in TD_UNPIVOT as optional.
    • Support for CREATE RECURSIVE VIEW.
    • Support for CAST to TIMESTAMP WITH TIME ZONE AT.
    • PIVOT can be a table alias, even if it is a reserved keyword.
    • Improved support for SUBSTR/SUBSTRING function, to allow undocumented but supported variants.
  • The Collibra Data Lineage servers now benefit from several parsing enhancements when integrating BigQuery data sources, including support for the construct (replace * modifier ).
  • The Apache Hive JDBC driver is now upgraded from 2.6.17.1020 to 2.6.19.2022.
  • Quoted identifiers in Microsoft SQL Server dialect are no longer case-sensitive. (ticket #85021)
  • If a Power BI dataflow specification does not contain entities, the attempt to process entities is skipped. (ticket #70082)
  • Harvesting Tableau metadata via a proxy server no longer results in a TCP connection timeout error. (tickets #84759, 85620)
  • Fixed an issue when synchronizing Tableau that resulted in the error message "A mapping for the external system id and resource already exists". (tickets #82323, 85018, 85132)
  • Fixed an issue in the technical lineage viewer that resulted in an HTTP 410 Gone error.
  • Fixed an issue in the technical lineage viewer that resulted in an HTTP 410 Gone error.
  • Fixed an issue in the Power BI harvester that caused an expired token error.
  • Fixed an issue in the merging algorithm that combines data from multiple data sources, which was causing unintended behavior in the Technical lineage viewer. (tickets #84780, 84925)
  • Fixed a lineage harvester issue that was slowing the ingestion of columns. (tickets #84796, 84923)
  • Collibra Data Lineage now correctly traces to the underlying table when processing SELECT INTO statements targeted at a view.

Data Governance

  • You can again select asset types within a subcommunity when you create an advanced filter. (ticket #80756)
  • Using the touchpad to scroll horizontally in a table no longer causes your browser to return to the previous page.
  • The scope icon no longer shrinks when the screen width changes or the left side of the screen is minimized.
  • The Move Assets dialog box now closes correctly after moving assets from a table view. (ticket #85470)
  • The domain type of the packaged 'Data Quality Dimensions' domain is now changed to Governance Asset Domain so you can create Data Quality Dimension assets in that domain. Note that this change is only done if you haven't edited the assignment of the Data Quality Dimension asset type. (ticket #75133)
  • The community overview table no longer disappears when you create a new community that is not part of the current community.
  • The community hierarchy immediately shows domains that are added in subcommunities.
  • The attachments page with a saved sorting order by date now correctly sorts the attachments when opening the page. (ticket #83219)
  • In the tables of the Operating model, cell changes can no longer be saved with no value or with spaces only. In these situations, the Save button is disabled.
  • In the basic filter pane of an asset table, you can again see the asset type in the Properties section if filtering on asset type would only return one result.
  • In the Add assignment window, scopes are now listed in alphabetical order.
  • Fixed a layout issue with the radio buttons and scope names in the Add assignment window.
  • Exporting assets with identical display names no longer causes a discrepancy in the number of exported assets under certain conditions. (ticket #78745, 83349)
  • Editing the community name on a community overview page is now immediately in the table.
  • Collibra no longer stops responding when adding a boolean attribute during the creation of a complex relation type.
  • A 'Save for all users' option for complex relation tables is now shown only to the users with the right permission. (ticket #81238)

Diagrams

  • You can again start a new diagram from a node. (ticket #77428)
  • When saving an edited diagram, the diagram view is overwritten instead of saving a new diagram view.

Edge

  • You can click the buttons at the bottom of a capability with a large number of manifest fields.
  • An Edge site installation no longer fails if secrets that are used during the installation contain special characters.

Search

  • The quick search on the References tab is no longer case-sensitive. The search criteria don’t only involve full expression but also parts of it.

Collibra for Mobile

  • You can again start workflows in Collibra for Mobile.
  • On Android, the keyboard no longer disappears when trying to add text in text fields. (ticket #87239)

Browser Extension

  • The Content Security Policy (CSP) no longer blocks images from loading in the Browser Extension.
  • The Browser Extension no longer crashes when using it on a Sharepoint website.
  • The "Add bookmark" button is now fully clickable, not only the upper half.
  • Improve the error message when trying to access an asset that does not exist after switching to another Collibra environment.
  • Clicking the link "Not what you are looking for" no longer shows "null" in the search field.
  • Auto-matching in Power BI now supports more asset types.
  • "Search in Collibra" from the context menu now opens the Browser Extension automatically.

Security

  • If you enter a wrong password too many times, your password status is set to inactive instead of your user account being disabled. An administrator will have to reset your password.
  • If you change the email address of a user, Collibra now sends a notification via email to the old email address.
  • A CSRF token is no longer missing from the response when no cookies are set for the auth/session API. (ticket #83781, 83808, 83822, 83862, 83892, 83920, 84009, 84054, 84164, 84182, 84455, 84767, 85028)

API

  • You can no longer create a scope overlap via a GraphQL call.

Patches

Patch 1

  • Jobserver now anonymizes data correctly even if you changed the data type of more than one column with the same name in a schema. (ticket #87006). A new Jobserver version is available, version 2022.05.1-67.
  • Fixed an issue where the upgrade stopped because custom characteristics are added to the 'Power BI Server', 'Power BI KPI', or 'Power BI Parameter' asset type in the environment.
  • Fixed an issue where the upgrade could fail when reading a translation file that contains non UTF-8 characters.

Patch 2

  • You no longer get a DataFetchingException error if historical guest users exist in the database and you open the Users page. (ticket #87959, 88857)

Patch 3

  • 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)
  • You can now create and edit complex relations in fewer steps.

Lineage harvester patch 1

  • Technical lineage Edge capabilities now run without having to set the QueryPassthrough parameter to “true” at the connection level.
  • The lineage harvester on Edge now logs all errors from the load source phase.

Edge capability patch 1

  • When you specify an invalid region name in the AWS region restriction console configuration, an error is now reflected in the logs.
  • At the start of an S3 synchronization process, the search for previous AWS Glue databases now respects the AWS region restriction rules.

2022.04

Release information

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

Metamodel Changes

  • We have renamed the S3 Catalog domain type to Storage Catalog.
  • We have moved the following packaged asset types:
    • S3 File System is now a subset of File Storage.
    • S3 Bucket is now a subset of File Container.
    • Directory is now a subset of File Container.
  • We have added the flowing new packaged asset types:
    • GCS File System: An asset type that represents Google Cloud Storage file system as a subset of Technology Asset → System → File Storage.
    • GCS Bucket: An asset type that represents a Google Cloud Storage bucket as a subset of Technology Asset → File Container.
    • File Storage: An asset type that represents a Cloud File Storage bucket as a subset of Technology Asset → System.
    • File Container: An asset type that represents Cloud File Container as a subset of Technology Asset.

Enhancements

Data Catalog

  • You can now use partial scan to profile most columns of Impala data sources via Edge, except for those in views, Kudu tables, and HBase tables.
  • You can now configure the maximum number of rows used by the Edge classification service in the "Maximum number of samples" field. See Configure data profiling behavior
  • You can modify the resource and CPU assignments of a data source by adding additional properties to the Catalog JDBC Ingestion Edge capability. We recommend to only add these properties together with Collibra Support. See Add an Edge capability to an Edge site.

Data Lineage and BI integrations

  • You can now use a databaseMapping property in your Tableau <source ID> configuration file, to map a Tableau technical database name to the real database name.
  • Collibra Data Lineage now supports calculated fields for embedded data sources that are published.

Edge

  • You can now install an Edge site on your own dedicated AWS EKS cluster.
  • The Edge site installer has a new option to allow explicit use of a resolver configuration file.
  • For managed Kubernetes (EKS), there is no more prerequisite on CPU and memory capacity of worker nodes.
  • Edge management user interface can now handle Cross-Site Request Forgery (CSRF) tokens.
  • Argocd is updated to mitigate a security vulnerability. You need to reinstall your Edge site with the new installer if you want to apply this argocd security patch. However, we recommend you check with your company's security policies if a reinstallation is required since the security risk is low.

Search

  • The Status facet is now a multi-select facet, meaning that when you are filtering search results, you can now simultaneously filter on more than one asset status.

Security

  • The user input in the default email templates is now encrypted. Unsafe characters are replaced with safe versions.

Miscellaneous

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

Fixes

Data Catalog

  • Jobserver jobs that fail during the finalization step now receive the status Failed instead of running indefinitely. (ticket #82221)
  • If you try to synchronize a Database asset with no assigned Owner, Collibra now shows an adequate error message. (ticket #81206)
  • If you modify the refresh schedule or the profiling / sampling options of Schema assets, Collibra no longer tests the connection to the data source via Jobserver. (ticket #77126, 80740)
  • Attributes containing plain text with special characters (<>) now expand correctly in tables, also when Catalog experience is disabled. (ticket #72613)

Data Lineage and BI integrations

  • When providing connection definitions for Informatica PowerCenter, the dbname property is no longer case-sensitive. (ticket #81810)
  • When integrating Informatica PowerCenter, Collibra Data Lineage now replaces parameters starting with a single "$" inside extracted queries. (ticket #83807)
  • When integrating Informatica PowerCenter, Collibra Data Lineage now correctly creates a technical lineage when useCollibraSystemName is set to true. (ticket #81721)
  • When harvesting parameter files in Informatica Intelligent Cloud Services data sources, parameters (including those with numbers in their names) in SQL overrides are now correctly matched. (ticket #73786)
  • The Teradata JDBC driver is now upgraded to version 17.10.00.27.
  • The MySQL JDBC driver is now upgraded to version 8.0.28.
  • The lineage harvester now supports InOut parameters for mapping tasks when harvesting metadata from Informatica Intelligent Cloud Services data sources. The parameters are now loaded and their values are used to replace variables in custom SQL queries. (ticket #80090)
  • The ingestion of Tableau Worksheets and Tableau Dashboards no longer results in an error when the external system ID already exists in Data Catalog.
  • The display name for Looker Data Set assets now uses the 'label' property, which provides an easier-to-read name.
  • The Collibra Data Lineage servers now benefit from the following parsing enhancements when integrating Snowflake data sources (ticket #85490):
    • Support for CONNECT BY after WHERE clause.
    • Support for TOP.
  • Fixed an issue that resulted in a parsing error indicating that the useCollibraSystemName property was set to “true”, when it was set to “false”. (ticket #82448)
  • Fixed an issue in the REST API pagination.
  • Fixed an issue in the lineage harvester that was causing random occurrences of newline characters in ingested Teradata objects.
  • After synchronizing a data source, the time is now accurately shown in the Last sync time column on the Sources tab page. (ticket #82213)

Data Governance

  • You can once again open communities in a new tab page from a link. (ticket #80081, 81342)
  • You can once again clear date attributes using the Clear button. (ticket #77838)
  • You can now only create assets in a domain whose type is allowed in the asset type's assignment. (ticket #72942)
  • The Pictures table once again refreshes automatically.
  • The Automatic Hyperlinking feature now handles special characters such as hyphens and slashes better. (ticket #80158)
  • In the history of a community, domain or asset, if you select a user other than the signed-in user as the Who filter, and then apply an Action filter, the history of the selected user is now shown, instead of the signed-in user.
  • Fixed an issue with the pagination of asset tables when you open the preview pane.
  • Fixed an issue with the Load More button on the History page.
  • Fixed an issue with inherited permissions, where all relevant domains are again available when moving assets. (#81272, 81501, 81592, 81612, 81727, 81794, 82017, 82327, 82418, 82630, 83593, 83601, 83922, 83970, 84768, 84828, 85060, 85470, 85572)
  • Fixed an issue which caused incorrect Last Login data time to be shown in exported CSV.
  • Fixed an issue in the Complex Relation Type field when importing complex relations. (ticket #75736)

Diagrams

  • Sharing diagram pictures no longer results in an error.
  • Diagram overlays and the Preview pane now show dates in the same time zone. (ticket #78000)

Edge

  • Spring Boot on Edge is upgraded to 2.6.6 to fix a security vulnerability. (ticket #85853)
  • If a Glue crawler fails during the S3 synchronization on Edge, the Support team can now retrieve log details to investigate the issue. (ticket #74144)
  • Fixed an issue in the Technical Lineage Edge capability so that you can again set the "Use Collibra system name" field to "true".

Browser Extension

  • The number of relations on an asset page in the extension now match with the number of its web version.
  • The selected filter now remains active when closing the extension overlay.
  • Improved auto-matching when navigating inside Tableau projects.
  • The Tiles accordion is now shown from the first time when visiting a Power BI dashboard.
  • All relations information on an asset page is now the same as in the web version.
  • Removing a domain from the extension's configuration is now automatically saved.

Security

  • A CSRF token is no longer missing from the response when no cookies are set for the auth/session API. (ticket #83781, 83808, 83822, 83862, 83892, 83920, 84009, 84054, 84164, 84182, 84455, 84767)

API

  • Τhe REST API endpoint GET/responsibilities now returns the expected results when specifying "type=RESOURCE". (ticket #69322)
  • You can again use the 'BETWEEN' filter in the Output Module. (ticket #83068, 83202)
  • Retrieving relations or complex relations in batches using the REST or Java APIs no longer creates overlapping content in the results. (ticket #80323)

Patches

Patch 1

  • You can now profile schemas via Edge that include more than 1,000 tables. (ticket #86838, 87179)
  • Asset tables can again accommodate more than 10,000 assets. (tickets #81689, 85774, 86242, 86315, 86529, 86614, 86657, 86660, 86717, 86887, 87492, 87535)

Lineage harvester patch 1

  • You can now use the optional concurrencyLevel property in the lineage harvester configuration file, to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. (tickets #82323, 85617)
  • The PostgreSQL JDBC driver is now upgraded from 42.3.2 to 42.3.3.
  • The lineage harvester no longer hangs when harvesting metadata from certain data sources.
  • The lineage harvester automatically refreshes Tableau tokens. (tickets #82323, 85617)
  • The Apache Hive JDBC driver is now upgraded from 2.6.17.1020 to 2.6.19.2022.

Edge capability patch 1

  • When you specify an invalid region name in the AWS region restriction console configuration, an error is now reflected in the logs.
  • At the start of an S3 synchronization process, the search for previous AWS Glue databases now respects the AWS region restriction rules.