Known issues for Data Privacy
The following limitations and known issues apply to Data Privacy.
Updates to advanced data masking rule are not reflected when rule logic is changed or deleted
When data masking vaulted assets and a rule configuration is deleted, updates to the advanced data masking rule are not reflected in the Asset tab of a dashboard to preview the asset.
To work around the update limitation, you must click the refresh icon 
in the Asset tab of a catalogs dashboard to preview the asset.
Applies to: 4.5.3
Data Privacy job fails with QPE005 if masking method is obfuscate
Custom class regular expression (regex) pattern is not available, which causes obfuscate to break hence format preserving obfuscate does not work. The workaround is to use redact or substitute, or other identifier obfuscate instead
of the custom class regex pattern.
Applies to: 4.5.3
Masking flow jobs fail in the default Spark 3.2 environment
To work around masking flow jobs that fail in the default Spark 3.2 environment:
- Open the project where you're running masking flow jobs.
- Click Manage and create a new Spark environment.
- From Software version, select Scala 2.12 with Spark 3.2.
- Create a new masking flow job.
- When you're defining details for the job, from Select an environment, select the new Spark environment that you created.
Applies to: 4.5.1
The Partial redact option masks all of the sensitive data
The Partial redact option that is available for email addresses, social security number, credit card classes, and US phone numbers, does not do the partial masking. Instead the sensitive information is fully redacted.
Applies to: 4.5.0
Masking doesn't work if rules are created to obfuscate custom data classes
If rules are created to obfuscate custom data classes, masking doesn't work because the rule interpretation and policy generation fail. The failure is because a regex pattern isn't available. The An error occurred attempting to preview this asset error occurs during asset preview, and the QPE005: Unexpected empty policy. error occurs during masking flows.
If you create rules to redact or substitute custom data classes, masking works as expected.
Applies to: 4.5.0
get-cr-status could result in Failed after validating upgrade
When you're validating your upgrade to Cloud Pak for Data 4.5.0 and 4.5.1 and the get-cr-status results in Failed, it's possible that the dp-subset pods are stuck and preventing you from completing
the upgrade.
To work around this issue, restart the dp-subset deployment by using the following command:
oc rollout restart deployment dp-subset
Applies to: 4.5.0 and 4.5.1
Fixed in: 4.5.2
Applying advanced data masking options
Advanced masking options don't apply to catalog preview, download, and Data Refinery.
Applies to: 4.0.3
Fixed in: 4.5.0
Advanced data masking options are only enabled for data classes.
Applies to: 4.0.3
Data protection rules do not apply to data assets and connections in a project
Data protection rules do not apply to data assets and connections that were directly added to a project.Data protection rules protect data in catalogs and protects data in projects asset preview but not in projects.
Applies to: 4.0.3
Parent topic: Masking data with Data Privacy