Known issues
The following is a non-exhaustive list of issues that we have encountered in this release. We intend to fix these issues as quickly as possible.
|
Ticket |
Issue |
Found in |
Fixed in |
|---|---|---|---|
| 91500 | When importing assets or complex relations, testing the import fails if the user interface language is not set to English. | 2022.05, 2022.06, 2022.07, 2022.08 | 2022.09 |
| If you are using the Databricks connection driver version 2.6.25, you cannot use partial scan when profiling via Edge. | 2022.05 | 2022.08 | |
| If you do not fill in the optional fields, Access Key ID and Secret Access Key, in the S3 File System Connection Details page, an incorrect error message appears:
"Jobserver no longer available. Select another Jobserver."
To prevent this error, fill in the Access Key ID and Secret Access Key fields. |
2022.05 | 2022.06 | |
| 81272, 81501, 81592, 81612, 81727, 81794, 82017, 82327, 82418, 82630, 83593, 83601, 83922, 83970, 84768, 84828, 85060, 85470, 85572 | You cannot move assets between domains in different subcommunities that have the same parent community if the permission is only set on the parent community. As a workaround, ensure that you also have the necessary permission on the subcommunity level. | 2022.01, 2022.02, 2022.03 | 2022.04 |
|
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 don't see the relations to that asset, for example in views or on the asset page of the related assets. However, the History tab page of asset pages mentions all relations, even if you don't have view permissions for the related asset. |
2022.02 | To be determined | |
| Time-based review rules that were configured to trigger Time based asset review workflows on an annual basis, did not start at the beginning of the calendar year 2022. We strongly recommend that you review any Time-based Review Rule assets you have configured, to see if there are target assets that should be reviewed. Read more. | 2022.01 | 2022.04 (to be confirmed) | |
| A data source ingestion fails if a foreign key has the same name as a table. | 5.5 |
Common issues
-
The Collibra Data Intelligence Cloud 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.
- Workflows with different values for the
processRefattribute of theparticipanttag and theidattribute of theprocesstag are not working in Collibra 5.6.0 or newer, despite having worked in older versions. These workflows have invalid BPMN files that cause ajava.lang.NullPointerExceptionerror, visible in the Collibra Console logs. For more details, see the troubleshooting section.