Known issues and limitations for Data Privacy (Masking flow)

CreateContainerError cause problems to run Bulk copy jobs

Applies to: 5.0.0 and later

If you're using a CSI-based storage type with volumes of large number of files, consider disabling SELinux relabeling. SELinux relabeling can cause a CreateContainerError that can prevent you from running bulk jobs. This error is also known to happen when the Red Hat OpenShift Container Platform is upgraded from 4.12 to 4.14 release. To disable SELinux relabeling, see the steps specific for Data Privacy service in the Disabling SELinux relabeling topic.

Correction to error message display for customized data class in obfuscate masking methods

Applies to: 5.0.2
Fixed in: 5.0.3

The following misleading error message displays when you have a customized data class in an obfuscate masking method:

Regex expressions has not been provided for custom regex dataclass <class_ID>

The correction to this error message is:

Custom data classes without regex are not supported for preview.

Can't preview assets with date columns and watsonx.data as the protection solution

Applies to: 5.0.0 and later

In the asset preview page, which is known to happen for virtualized join views and watsonx.data connected data, the value for the Masked columns displays an incorrect count. In addition, the masked indicator icon image is either missing or incorrectly displayed from the header of columns with masked data. For details, see the Known issues and limitations for IBM Knowledge Catalog.

Unable to preview assets when row filters are applied in data protection rules

Applies to: 5.0.1 and later

If the column names of the assets include spaces and you apply data protection rules with row filtering, you cannot preview the asset and the following error displays:

Unable to show preview
Preview failed to load. Try again or contact your system administrator.

Workaround: To apply and preview row filters for assets in data protection rules, avoid specifying spaces in the column names. For example, use the column name First_name (instead of First name).

Details for masked columns display incorrectly

Applies to: 5.0.0 and later

For more information, see the Known issues and limitations for IBM Knowledge Catalog.

Unable to preview an asset with a row filtering rule due to connection restrictions

Applies to: 5.0.0 and 5.0.1
Fixed in: 5.0.2

You cannot preview an asset that uses row filtering when connection is configured with Mask sensitive credentials retrieved through API calls setting to On.

To preview the asset with a row filtering rule, the workaround is to set the Mask sensitive credentials retrieved through API calls to Off on your data source connection. For more information about configuring the Mask sensitive credentials retrieved through API calls setting, see Connecting to data sources topic.

Cannot truncate CHAR data type for Teradata in masking flow

Applies to: 5.0.0 and later

Masking flow job fail as CHAR data type cannot truncate for Teradata relational database. For example, the masking flow job fails with the following error message:

Character data truncation detected for the field <COLUMN_NAME>. The length of the value is 44 and the length of the target column is 26. (error code: INVALID_DATA)

The masked data output contains extra space padding even after the library truncates the data.

Parent topic: Known issues and limitations for IBM Cloud Pak for Data