Issue | Description |
|---|---|
CP-13408 | When you create a rule occurrence using a dimension that you previously deleted, the job fails. |
CP-13407 | Profile import fails if the data quality rule occurrence dimension that the profile uses does not exist in the target organization. |
Issue | Description |
|---|---|
CP-13222 | When you configure a fixed-width file in Data Integration and you update the defaut values in the advanced properties for the file, a profiling task that you run on the file ignores your updates. |
CP-13225 | When you import a profiling task that reads a fixed-width file that you created in Data Integration, the values that you specified for the formatting options are not retained. Workaround: Reset the formatting options after you import the task. |
CP-13086 | A profile job returns incorrect results when you drill down or create queries on patterns that are consolidated under the Others category. This issue occurs when you set the value of the Pattern Threshold Percentage to less than 0.11. |
Issue | Description |
|---|---|
CP-13106 | When you run a PostgreSQL native profile with the Minimum Number of Rows for Split Process per Column and Maximum number of columns per mapping advanced partitioning options, the options do not have an effect on the profiling results. |
CP-13104 | When you create a mapplet connection profile from a source mapplet with two joined SQL Amazon Redshift connections and run the profile, the job fails with the following error: Profile job failed with error null. |
CP-13082 | When you create a data profiling task with a PostgreSQL connection and specify advanced options, you can't select a mapplet as the source object. |
CP-13126 | When you try to import a profiling task from another organization through the profiling-service/api/v1/profile API, the import fails in the following case: The profiling task includes a Data Quality or Data Integration asset that you added to the task through the profiling API. Workaround: Use the PATCH /profiling-service/api/v1/profile/ REST API to update the profiling task description before you copy or export the task. |
Issue | Description |
|---|---|
CP-12722 | When you run a profiling task on a mapplet that includes an Amazon Athena source object with S3OutputLocation advanced options, the job is successful but the file is not retained in the specified output location. |
CP-12676 | A Rule Occurrence status appears as 'Acceptable' instead of 'Non-Acceptable' in the following scenario:
|
Issue | Description |
|---|---|
CP-12681 | When you re-import a data profiling task that includes rule occurrences, Data Profiling doesn't retain primary and secondary data elements attached to the rule occurrences in Data Governance and Catalog. |
CP-12676 | When you set a threshold value to 0-0, the rule occurrence status appears as Acceptable instead of Not Acceptable. |
CP-12665 | When you run profile on a mapplet that includes a Snowflake source object with a custom query, the job fails with the following error: Profile job failed with error null. |
Issue | Description |
|---|---|
CP-12385 | When you create a profile for a JDBC V2 source with the JDBCV2_MariaDB connection, and apply a filter on the Date or Timestamp column, the profiling task fails with an error. (April 2024) |
CP-12219 | When you export a source mapplet profile, execute it and reimport it to the source folder, the connections do not load on the Source Details pane of the profile. Workaround: Import the file to a different folder in the same organization. (February 2024) |
CP-12120 | You can download logs for profiling jobs if the Logs - View and Download feature is not enabled for your role on the Monitor service. (February 2024) |
CP-11456 | A profile job fails in the following scenario:
(October 2023) |