Known issues

The following table contains a non-exhaustive list of known issues.

Ticket

Known issue

Found in

Fixed in

Not applicable The Knowledge Graph API response body contains an additional "extensions" filed. 2023.11

2024.01

Not applicable History doesn't look properly when it is a part of Tasks pane on asset page. 2023.11

Under review

116059 To collect sample data via Egde, you need View permission on the Database asset linked to the asset for which you want to collect the sample data. 2023.05 2023.11
Not applicable When you integrate Databricks Unity Catalog, the maximum size per table is 256K.
If you try to synchronize such a big table, the integration won’t work. If Databricks Unity Catalog contains tables larger than 256K, exclude these tables by using the Filters and domain mapping field in the Databricks synchronization capability or by revoking the permissions to read those tables in Databricks itself.
2023.05 Under review
Not applicable Chrome or any Chromium-based browser such as Opera can have an impact on your Edge connections and synchronization capabilities.
If you saved your user name and password when signing in to Collibra and you later change the Edge AWS connection, then Chrome will automatically add your user name and password to the AWS connection parameter fields.
Chrome will do the same for the IAM role field in the S3 synchronization capability and for similar password-based fields in other Edge connections and capabilities such as ADLS.
Make sure to manually verify and, if needed, update the fields when you save a connection or capability.
2023.05 Not planned
Not applicable If an asset name contains a space and the allowedCharacters parameter in the tokenizer settings contains double quotation marks, the References tab of the asset page does not show results. 2023.05 Under review
Not applicable

After Usage Analytics is deployed, the following error message may be temporarily shown in place of the Usage Analytics dashboard: Your configuration restricts query requests to only be served from pre-aggregations, and required pre-aggregation partitions were not built yet. Please make sure your refresh worker is configured correctly and running.

This message disappears and the Usage Analytics dashboard is shown approximately 6 hours after the deployment.

2023.02 Under review
Not applicable Data Marketplace stops working if you try to save a relation index that contains a special character, such as /, ?, @, [, }, <, >, in the name or in one of the relations. 2023.02 Under review
Not applicable When exporting the CSV file of the user table, the Required license column uses the term AUTHOR for Standard license and CONSUMER for Read-only license. 2023.02 Under review
Not applicable

If you use the Google Translate extension to translate Data Marketplace, Homepage, or Usage Analytics, the application may stop responding.

Note To continue working without Google translation, refresh the page.

2023.02 This is a Google Translate extension issue.
Not applicable

Edge currently needs specific Edge only users to be created and assigned with respective Edge specific roles in order to function. These Edge only users consume a Standard license because of the roles and the permissions they have. However, as these Edge only users are purely system users they shouldn't be counted against the number of licenses being used. Therefore, we will allow all customers to exceed the license agreement for such Edge only users until this known issue has been fixed.

2022.11 Under review
Not applicable In Protect, when creating a data access rule, depending on the number of assets, the asset types, or the prescriptive paths, Protect may show all the data categories or data classifications for masking or row-filtering, including those that are not applicable to the selected assets. 2022.11 Not planned
Not applicable

In Protect, when creating a data access rule, if, after selecting an asset that contains masking and row filtering data, you apply masking and row filtering to the asset, remove the asset, and then select an asset that does not contain masking and row filtering data, the data from the previously selected asset is still retained and you can save the rule.

Note Although the rule is saved, the synchronization status fails as expected.

2022.11 Not planned
Not applicable Within 24 hours after Usage Analytics is enabled, if you do not sign in to Collibra Data Intelligence Platform or visit an asset, empty cards are shown on the Usage Analytics dashboard. 2022.11 Not planned
Not applicable The REST Import API returns an error when processing assets that have relations and the name of a related asset contains a comma. 2022.11 Not planned
Not applicable In Data Marketplace, it is possible that fewer or more search results appear on the All filter tab compared to other filter tabs. This is because the out-of-the-box filter tabs, Tables, Data Sets, and Reports are not impacted by the Data Marketplace scope configuration. Administrators can configure the available filter tabs. 2022.11 Not planned
Not applicable

The new licensing terms, Standard and Read-only, are being overwritten by the old terms, Author and Consumer, in some instances. This happens when language customizations have been made to the interface text.

You can see how to reset the interface text in our documentation.

2022.11 Not planned
Not applicable

From version 2022.11 onwards, Collibra takes the default language of your browser into account to select the interface text language of some sections. Collibra now also has translations of some interface text available out of the box. Consequently, you can no longer edit that interface text, nor translate it into unsupported languages. This includes the interface text of Usage Analytics, Data Marketplace and the Homepage. This means that the language of some user interface text may not always match the language settings in your user profile.

2022.11 Not planned
79928

Normally, you only see relations if you have view permissions for the head and the tail asset of the relation. If you do not have view permissions for an asset, you do not see the relations to that asset, for example, in views or on the asset page of the related assets. However, the History tab of asset pages mentions all relations, even if you do not have view permissions for the related asset.

2022.02 Not planned
Not applicable

The Collibra Data Intelligence Platform 5.7.2-13 release fixed performance issues with the Escalation Process workflow.

To take advantage of the improvements, you must deploy the new version of the Escalation Process workflow in your Collibra 5.7.2-13 or newer.

Note If you are using a modified Escalation Process workflow, you must port your changes to the new workflow.

Warning The new Escalation Process workflow is only valid for Collibra 5.7.2-13 or newer.

5.7.2-13 Not planned
Not applicable Workflows with different values for the processRef attribute of the participant tag and the id attribute of the process tag do not work in Collibra 5.6.0 or newer, despite having worked in older versions. These workflows have invalid BPMN files that cause a java.lang.NullPointerException error, visible in the Collibra Console logs. For more details, see the troubleshooting section. 5.6 Not planned
30943, 36378 Data source ingestion fails if a foreign key has the same name as a table. 5.5 Not planned