Release Notes for IDMC
- Release Notes for IDMC
- All Products
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-13102
| When you run a profile on Microsoft Fabric Data warehouse assets with the First N Rows sampling option, the profiling fails with the following error: [ERROR] Failed to run the Microsoft Fabric Data Warehouse mapping because of the following error: [Incorrect syntax near '5'.] |
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-6963
| When you import profiles created using the profiling-service/api/v1/profile API, the import fails with the following error:
400 Bad Request |
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)
|