Common Content for Data Engineering
- Common Content for Data Engineering 10.5
- All Products
Issue
| Description
|
---|---|
SATS-39840
| In a multinode domain, if you run the Data Privacy Management Service on a different node from the other services, the Process tab does not update for the service.
|
SATS-39666
| Database profile jobs do not complete.
|
SATS-39422
| If an Auto Sync Catalog job fails, all future triggered jobs fail.
|
SATS-39242
| User activity monitoring generates incorrect security policy violations based on user home location and data store groups.
|
SATS-39232
| UBA Manager fails if a security policy includes conditions with percentage or value changes.
|
SATS-39209
| A Row Count Collect job step for Hive sources includes rows that are not marked as sensitive.
|
SATS-38568
| A user group import job fails if the description includes the words "software update".
|
SATS-38524
| User activity events do not process as expected and cause Augmenter application errors.
|
SATS-38121
| Data store tags are truncated when you run a scan or Evaluate Classification Policies job.
|
SATS-38119
| A scan on unstructured sources gets stuck in the Evaluate Classification Policies job step.
|
SATS-38053
| You cannot use a Hive JDBC URL with length greater than 255 characters.
|
SATS-37868
| An Import Protection Status job skips columns that are not marked as sensitive.
|
SATS-37685
| The field length restriction of the Schema Names field for a data store does not allow you to select all required schemas.
|
SATS-37684
| The Subject Registry has performance issues.
|
SATS-37682
| The Confidence Level field is not included in the CSV file when you export data store details even though it is a required field when you import protection status.
|
SATS-37436
| Enterprise Data Catalog scans of Azure Data Lake data stores with Data Lake Store Gen 2 ADLS source type fail because the connection is created with Data Lake Storage Gen 1 instead of Gen 2.
Workaround: Create the connection in Informatica Administrator, and enter the ID value in the
Source Connection Name field in the data store creation page in Data Privacy Management.
|
SATS-31712
| You cannot see the Tables per Workflow and Max Parallel Sessions values on the Protection Task page.
|
SATS-31709
| Protection tasks fail with a TimeOut error.
|
SATS-31661
| The Load Catalog job step fails if the ROW_MATCH_COUNT is beyond the java integer limit.
|
SATS-31658
| A scan that uses a remote agent fails if the FILE_PATH includes more than 255 characters.
|
SATS-31656
| Evaluate Classification Policies jobs do not run, and remain in New state.
|
SATS-31653
| You cannot download a DSAR report if the subject name includes a comma.
|
SATS-31535
| Hive Test Connection fails if the ZooKeeper URL includes a comma-separated JDBC URL.
|
SATS-31534
| You cannot assign an Elasticsearch application to a specific YARN queue.
|
SATS-30680
| Upgrade requires that you populate the Subject Registry configuration file even if you have not created a Subject Registry in the previous version.
|
SATS-29920
| If you resume a remote agent scan job that failed because of a Data Privacy Management restart, the resumed job fails with a Duplicate pageId found error.
|
SATS-23096
| If you resume a scan job that fails, the resumed scan also fails.
|
SATS-21335
| Installing Data Privacy Management causes Identity Match to fail in Informatica Data Quality.
|
SATS-18677
| User privileges are not validated for access to specific pages.
|
SATS-18676
| Elasticsearch does not restrict users as expected based on authentication.
|
SATS-18675
| An SQL Injection error is noted when you sort columns.
|
Issue
| Description
|
---|---|
SATS-38058
| You can modify the number of containers for YARN applications like Percolator, Augmenter, and UBA Manager.
|
SATS-37685
| There is no field size restriction on entering of multiple schema names.
|