Issue | Description |
---|---|
SCAN-19989 | When you cancel a metadata extraction job, the job status moves to Failed instead of Cancelled. |
CDGC-78610 | When you run data quality jobs with rule occurences, the jobs skip rules that include invalid or missing output port mappings. However, the Monitor page in Metadata Command Center doesn't display the skipped rules in Skipped Rule Occurences and no debug logs are generated. |
Issue | Description |
---|---|
MDP-4190 | When you run multiple jobs with merge operations that have object references across multiple source systems, the jobs complete with errors in the DEBUG log or fail with the following error: Indexing failed |
Issue | Description |
---|---|
SCAN-13790 | When you run a metadata extraction job on an SAP Datasphere catalog source, the job fails with the following error: Could not execute Datasphere API This issue occurs when the access token for the client ID expires. Workaround: Generate a new access token for the client ID in Administrator. |
Issue | Description |
---|---|
SCAN-12619 | Metadata Extraction jobs fail to parse Databricks Python pipeline activities for Microsoft Azure Data Factory catalog sources and the following error occurs: ERROR (DefaultPlSqlFunctionCallVisitor:248) {/prod-ara-adf/Copy_To_Information_Factory_Pipelines/PL_Incremental_Copy_Archer_TO_InformationFactory/PL_Incremental_Copy_Archer_TO_InformationFactory_23ad8e46-e97a-4e9a-9c19-dca99a41058f/ForEachSequenceLcm/TodeletedataLcm} - Cannot resolve uspDeleteIFdata neither as a PL/SQL object nor type. |