Only show release notes of Collibra Platform for Government-certified features

Release 2024.03

Release information

  • Publication dates:
    • Release notes: March 5, 2024
    • Documentation Center: March 5, 2024
  • Release date of Collibra 2024.03.0: March 10, 2024
    • Upgrade non-production environments: March 10, 2024
    • Upgrade production environments: March 31, 2024
  • Release date of Collibra 2024.03.1: March 24, 2024
  • Release date of Collibra 2024.03.2: On demand only
  • Release date of Collibra 2024.03.3: April 8, 2024
  • Release date of Edge 2024.02-0: February 4, 2024
  • Release date of Edge 2024.02-14: February 18, 2024
  • Release date of Edge 2024.02-21: February 25, 2024
  • Release date of Edge 2024.02-28: March 3, 2024
  • Release date of Edge 2024.02-42: March 17, 2024
  • Release date of Edge 2024.02-49: March 24, 2024
  • Release date of Edge 2024.02-63: April 7, 2024
  • Release date of Edge 2024.02-70: April 14, 2024
  • Release date of Edge 2024.02-77: April 21, 2024
  • Release date of Edge 2024.02-105: May 19, 2024
  • Release date of Edge 2024.02-112: May 26, 2024

Highlights

  • Collibra AI for Descriptions (in preview)

  • Collibra AI can now help accelerate the creation of descriptions for assets in Collibra, making your data easier to understand.

    • Collibra AI can help to create a description for a Column, Table, Database View, or Data Set asset.
    • In Table assets, Collibra AI can also help to create descriptions for all columns in the table in a single action.

Enhancements

Workflow Designer

  • You can now apply translations to the forms of workflows created in Workflow Designer. (ticket #134501)

    Note This feature isn't available in the latest UI.

Fixes

Data Catalog

  • In the Unified Data Classification method, selecting data classes in the Data Classification page no longer changes the sorting order of the table.
  • The data buffer in the Sampling capability has been increased to enable the extraction of larger samples.
  • We increased the stability of the JDBC ingestion via Jobserver. (ticket #127919, 131414)

Data Lineage and BI integrations

  • When integrating Looker, Google API errors are now correctly handled and the log files clearly indicate what the error was and which metadata was skipped because of the error. (ticket #134646)
  • When integrating Power BI, if you configure workspace filtering but include an invalid workspace, the lineage harvester skips the invalid workspace and logs it. If the filter configuration includes only invalid workspaces, integration fails. (ticket #127036, 130372)
  • When integrating Power BI:
    • If the harvester connection to Power BI expires, the connection is now automatically reestablished, instead of triggering a time out error.
    • If you enter incorrect Power BI credentials, the ingestion job fails as expected, but now the log files better explain the related issue.

    These fixes help reduce the chances of HTTP 401 and HTTP 403 errors.

  • All Collibra Data Lineage service on Azure are sunset.

Workflows

  • Using a variable as the href value in a workflow form no longer creates an empty link. (ticket #131702)

Collibra Console

  • The password reset process for Collibra Console is no longer case sensitive. (ticket #134985)

Security

  • To avoid high memory utilization, the default maxIdle value of the AuthPermissions cache is now one day.

API

  • Using the /files endpoint of the REST Core API v2 to upload a file without a file name, such as plain text, no longer causes a null pointer exception. (ticket #133130)

Miscellaneous

  • We have improved the security of Jobserver.
  • We fixed an issue for community filters so that recommended assets show up on the Homepage and in Data Marketplace. (ticket #135754 )

Featuresin preview

A public preview is an upcoming feature or product that is made available to all customers before it is fully ready for general availability so it can be tested and evaluated early. Learn more

Data Catalog

  • Collibra AI can now help accelerate the creation of descriptions for assets in Collibra, making your data easier to understand.
    • Collibra AI can help to create a description for a Column, Table, Database View, or Data Set asset.
    • In Table assets, Collibra AI can also help to create descriptions for all columns in the table in a single action.

Data Lineage

  • You can now share database models across data sources. Sharing database models allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This mitigates analysis errors and allows for a complete lineage that includes lineage from the SQL statements from dependent data sources. For complete details, go to Sharing database models across data sources.

New look and feel

  • We have fixed an issue where the user mentioned in comments on asset pages would not display correctly.
  • We have resolved an issue for assets where links from notification emails generated from the latest UI didn’t lead to the expected associated comment.
  • Removing a filter from the Tasks page after having added or removed table columns no longer causes an error.
  • Proposed values in an asset drop-down workflow form are now at the top of the list.
  • Long workflow tasks names take up a maximum of two lines before being trimmed.
  • Starting a workflow which contains a start form from a workflow dashboard widget no longer shows an empty dialog box.
  • Date workflow form components no longer show suggestions for the input field.

Collibra maintenance updates

Collibra 2024.03.1

  • If you start and submit an assessment before registering the subject AI use case, the “Copy assessment answers to AI Use Case asset” workflow is no longer triggered. This is the intended functionality, because if the use case hasn't been registered, there is no asset page to copy the assessment answers to.
  • You can now register a new AI use case from the Legal Reviewer landing page. As a reminder, to access the Legal Reviewer landing page, you need the AI Legal Reviewer global role. You also need certain permissions to register a new AI use case. For complete information, go to Set up AI Governance.
  • When you edit a data access rule, the groups are once again shown in the description and the selection fields. (ticket #136515)
  • We improved the wording in error messages of Protect. (ticket #137024)
  • The Data Classification fields in data protection standards and data access rules now show all classifications, in alphabetical order.
  • Protect now loads the synchronization delay interval correctly from Collibra Console and uses the last configured interval if it can't retrieve the current interval.
  • Collibra data entry asset components that retrieve more than 1,000 proposed values in a workflow task no longer cause an error. (ticket #136622, 137219)
  • We have improved performance of loading asset views on community pages. (ticket #138211)
  • Relation reindexing now continues even if the confirmation response times out during the indexing request. (ticket #138154)

Collibra 2024.03.2

  • You can now bulk delete assets without a long wait time. (ticket #140748)

Collibra 2024.03.3

  • When certain activities are completed, the user who made the change is logged in the History tab. We have fixed an issue which resulted in the wrong user being listed as the user who made the change. Any changes made after the 2024.03 release, may have been impacted by this issue. With this fix, the correct user will be listed on the History tab for new changes. (ticket #142595, 142462, 141198, 140792, 142520, 142427, 142763, 142948, 143061, 142818)

    Note For changes made between 2024.03 and this fix, we are working to amend the incorrect user history. We will provide you with an update when we have more information on this.

  • Responding to workflow action emails works again as expected. (ticket #139637)
  • The performance of relational indexing is now improved significantly. (ticket #138154)
  • An API request to modify a resource locks again that resource, preventing other API requests from modifying the same resource while the request is under way. (ticket #139836)

Data Lineage 2024.03.1

  • When integrating Power BI with DAX analysis enabled, we have improved the error messaging in the source code to better inform you in case of the following scenarios:
    • The Collibra Data Lineage service instance can't parse the DAX analysis result returned from Vertex AI.
    • Vertex AI didn't return analysis results for a particular expression.
    • You've reached the character limit, as described in DAX analysis via Collibra AI. (ticket #137338, 138202, 138324)

Data Lineage 2024.03.2

  • Power BI expressions are now handled in a non case-sensitive manner. The Collibra Data Lineage service instances can now correctly identify the columns referenced in Power BI expressions, regardless of any capitalization discrepancies in the names of the columns. This will reduce the chances of experiencing the following error: "Column '{parsed_column}' not found in table '{parsed_table.table_name}' or any related tables within the dataset.” (ticket #136903, 137394) (idea #DCC-I-2960)

Data Lineage 2024.03.3

  • When viewing the technical lineage of Teradata data sources, if you right-click on a node and select “Transformations (IN/OUT)” to show the incoming or outgoing source code fragments, the complete SQL statements are now shown in the source code pane. Before this fix, the SQL statements were sometimes incomplete. (ticket #138739, 139949)
  • Previously, Collibra Data Lineage encountered issues when parsing parameters with similar prefixes in DataStage, such as $$db and $$db_test, leading to incorrect resolution. For instance, if you have the definition of $$db = PRODDB, the value of $$db_test would mistakenly become PROD_DB_test. This issue could result in incorrect database, schema, table, or column names in the technical lineage graph, depending on parameter usage. Collibra Data Lineage now resolves parameters by length in descending order, ensuring that the longest matching parameter takes priority for resolution, thus resolving the issue effectively. (ticket #139303)

Data Lineage 2024.03.4

  • The new batch definition option when creating a custom technical lineage is now generally available. Benefits include:
    • Support for indirect and table-level lineage as well as column-level lineage.
    • Support for any asset type with stitching.
    • You can now submit multiple JSON files.
    • You no longer have to define every asset used in lineage relation in a separate section.
  • When integrating Power BI with DAX analysis enabled, Collibra Data Lineage now clearly identifies which columns are measures and which are calculated columns. (ticket #130635)
  • When integrating MicroStrategy, database mapping and schema mapping, as configured in your <source ID> configuration file, now work as intended. (ticket #136578)
  • Collibra Data Lineage now supports the Power Query M function SapBusinessWarehouse.cubes.
  • The Tableau integration supports Salesforce Data Cloud data sources; however, to obtain stitching, you have to configure host name mapping in your <source ID> configuration filewith "found_hostname=*", because the Tableau APIs don’t return a host name.
    "hostnameMapping": {
	"found_dbname=databasename1;found_hostname=*;found_schema=test": {
		"dbname": "mssql-database-name",
		"schema": "mssql-schema-name",
		"dialect": "mssql",
		"collibraSystemName": "mssql-system-name"
	}
}
  • When you create technical lineage for DataStage, Collibra Data Lineage now supports parameter sets with parameters set to As pre-defined.

Edge and Data Lineage updates

These updates contain security and bug fixes for Data Lineage, Edge sites and their capabilities. These releases may be planned outside the regular monthly or quarterly release. You'll see the fix versions if you are manually upgrading an Edge site or reviewing logs.

February 18, 2024
(collibra-edge-2024.02.14-12)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Infrastructure

  • New Edge sites can now be installed on the following managed, dedicated clusters:
    • Azure Kubernetes Service (AKS)
    • AWS Fargate using EKS
    • Google Kubernetes Enginer (GKE)
    If you subscribe to any of these kubernetes services, you can now operate your Edge site with system requirements that are aligned to your preferred platform.
    Note 
    • Edge sites deployed on EKS or k3s are not impacted and can't be migrated to a new kubernetes cluster.
    • Forward proxies are not currently supported for Edge sites installed on a new kubernetes cluster.
  • We fixed an issue where Classification via Edge did not work because the imagepullsecret value was empty within the Collibra-edge application. With this fix, Classification via Edge works as expected. (ticket #136295, 136575, 136703, 136710, 136782, 136892, 136893)
  • Kubernetes has released a patch which removes the Leaky Vessels vulnerability. You will need to ensure you upgrade your kubernetes version to ensure you receive this patch.

Protect

  • Protect for AWS Lake Formation can now handle columns that contain partition keys.

Data classification

  • We updated the Sampling and Data Classification capabilities to allow the request for sample data from Snowflake. (ticket #137053)

Metadata integrations

  • The new Dataplex Location field is added to the synchronization configuration page for Google Dataplex Catalog. With this new field, you can add any new Dataplex locations when you synchronize the capability.

Technical lineage

  • Technical lineage for Databricks Unity Catalog can handle arbitrary amounts of data.

February 25, 2024
(collibra-edge-2024.02.21)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Infrastructure

  • We fixed an issue where Edge sites failed to be restored from backups that were larger than 1MB. (ticket #135278)

Data classification

  • We have improved the security of data classification.

Technical lineage

  • When integrating JDBC data sources via Edge, with the Shared Storage Connection method, you can now use the new Database-System Mapping field to map specific databases to specific systems, to obtain stitching. Previously, stitching was missing, as all databases were associated with the default system name provided in the Collibra System Name field.

March 3, 2024
(collibra-edge-2024.02.28)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Infrastructure

  • New Edge sites can now be installed on a managed, dedicated OpenShift kubernetes cluster. If you subscribe to OpenShift services, you can now operate Edge with system requirements aligned to your preferred infrastructure.
    Note 
    • Edge sites deployed on EKS or k3s are not impacted and can't be migrated to an OpenShift cluster.
    • Forward proxies are not currently supported for Edge sites installed on an OpenShift cluster.

Technical lineage

  • When integrating Power BI via Edge or the lineage harvester:
    • If the harvester connection to Power BI expires, the connection is now automatically reestablished, instead of triggering a time out error.
    • If you enter incorrect Power BI credentials, the ingestion job fails as expected, but now the log files better explain the related issue.

    These fixes help reduce the chances of HTTP 401 and HTTP 403 errors.

March 17, 2024
(collibra-edge-2024.02.42)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Security

  • We have improved the security of Edge.

Collibra Protect

  • Protect for BigQuery no longer reports an error when a schema or table does not exist.

March 24, 2024
(collibra-edge-2024.02.49)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Security

  • We have improved the security of Edge, Data Classification via Edge, Collibra Protect, Dataplex synchronization, Databricks Unity Catalog synchronization, ADLS synchronization and Technical Lineage for Databricks Unity Catalog.

Technical lineage

  • When creating technical lineage for SAP HANA data sources, the order of the columns (and the associated lineage) in views is now correct.

April 7, 2024
(collibra-edge-2024.02.63)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Infrastructure

  • We fixed an issue where Edge JDBC logging output files were missing from the Edge site. With this fix, these output files are available on the Jobs tab, as expected. (ticket #141484)

Security

  • We have improved the security of the ADLS, Databricks, and GCS Dataplex synchronization via Edge, and the Technical Lineage for Databricks via Edge.

Protect

  • Protect for BigQuery can now update tables containing columns of type RECORD or STRUCT. (ticket #139635)
  • Creating data access rules using data classes with overlapping columns no longer leads to Protect incorrectly reporting masking conflicts. (ticket #139268)

Technical lineage

  • When you created technical lineage for Databricks Unity Catalog, the technical lineage graph excluded tables that did not have lineage information. Now, the technical lineage graph accurately includes all tables collected from Databricks Unity Catalog, regardless of whether lineage information is present. (ticket #137243)
  • When you create technical lineage for Databricks Unity Catalog, Collibra Data Lineage now collects unique lineage entries from the lineage table. This enhancement expedites the process of creating technical lineage for Databricks Unity Catalog.

April 14, 2024
(collibra-edge-2024.02.70)  

Technical lineage

  • We made small improvements to a feature that is currently in private preview.

April 21, 2024
(collibra-edge-2024.02.77)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Security

  • We have improved the security of Data Classification.

Collibra Protect

  • Creating data access rules using data classes with overlapping columns no longer leads to Protect incorrectly reporting masking conflicts. (ticket #139268)
  • Protect for BigQuery can now update tables containing columns of type RECORD or STRUCT. (ticket #139635)

Metadata integrations

  • A Databricks access token with the BROWSE privilege can now also integrate metadata from Databricks Unity Catalog. It doesn't require the USE CATALOG and USE SCHEMA privilege. (in preview) (ticket #141283)
  • We fixed an issue where the ADLS synchronization failed because of special characters, such as { { ! * ' ( ) ; : @ & = + $ , ? % # [ ] . } in names. (ticket #136498)

Technical lineage

  • When ingesting Snowflake (SQL mode) via Edge or the lineage harvester, Collibra Data Lineage now harvests the metadata of stored procedures. We are currently doing the backend work to be able to generate lineage for stored procedures. We will keep you informed of our progress.
  • When enabling technical lineage via Edge, you no longer have to configure any of the following settings via Collibra Console or the Collibra Settings. They are now obsolete.
    • Power BI and Tableau synchronisation enabled
    • Technical lineage via JDBC connection enabled
    • Technical lineage for SQL via folder, ETL tools, and custom lineage on Edge enabled
  • Updated an SQL query to harvest data object names when ingesting Teradata data sources, to mitigate failure during ingestion.
  • The new Time Frame field is added to the technical lineage for Databricks Unity Catalog capability for you to specify the days of data that Collibra Data Lineage collects when creating technical lineage for Databricks Unity Catalog. This field is required, so you must enter a value before synchronizing the capability.

May 19, 2024
(collibra-edge-2024.02.105)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Security

  • We have improved the security of Edge, Catalog JDBC ingestion, JDBC Profiling, Catalog Data Classification and Catalog JDBC Sampling.

May 26, 2024
(collibra-edge-2024.02.117)  

This is the version of the Edge release. You'll see it if you are manually upgrading an Edge site or reviewing Edge logs.

Security

  • We have improved the security of Edge.