Known issues in Cloudera Data Catalog (1.5.3-CHF1)
This section lists the known issues in this release of the Cloudera Data Catalog service.
- CDPDSS-3346: Profiler pods are stuck in init state
- The
CDP_ACCESS_KEY_ID
andCDP_PRIVATE_KEY
keys do not receive values when upgrading from Cloudera Data Catalog 1.5.2 to 1.5.4. - CDPDSS-3057: Failed profiler job because of missing columns in log entries.
- When the logs to be profiled by the Ranger Audit Profiler have
missing columns, the profiling job fails. The ranger audit profiler pod log contains the
following message:Ranger Audit Profiler failed: Failed
to run Ranger Audit Profiler. Error: "['column1',
'column2', ...] not in
index".
column1
,column2
show the missing column entries in the logs.Each Ranger audit profiler job has 3 sub-jobs (identified by the same job ID prefix), any of which could fail because of the above reason. It is possible that one or even two sub-jobs pass till the above scenario is encountered.
- CDPDSS-3081: Datasets: Tenant Schema is getting passed as workload username while impersonating a user on ATLAS and Ranger API calls
- While making API calls to Apache Atlas and Apache Ranger, there
is a potential bug in code where a wrong value for
workloadUserName
is getting passed which causes the APIs to perform an auth check with a wrong parameter, causing unwanted issues. - CDPDSS-3080: Deleted Entities in Atlas cannot be removed from Datasets
- Entities deleted in Apache Atlas cannot be removed from Cloudera Data Catalog datasets.
- CDPDSS-3048: Filtering based on Job status Finished is not working
- The profiler job filter Finished is working correctly now, displaying the relevant jobs.
- CDPDSS-3042: Edit classification is failing with guid undefined error
- Trying to edit the classifications in the Asset Details screen can result in the "List properties for entity request failed Error from Atlas. Not Found : Received 404. Body {\"errorCode\":\"ATLAS-404-00-005\",\"errorMessage\":\"Given instance guid undefined is invalid/not found\"}" message.
- CDPDSS-3037: Asset Details page does not highlight link for Datasets
- The Asset Details now correctly highlights links to Datasets.
- CDPDSS-3524: Profiler pod launch is failing with init error
- During the profiler cluster setup, when all the services pods
are being deployed, Cloudera Data Catalog attempts to complete the prerequisites to set up a
service and request to create a machine user. If the UMS service has not come up properly at
that time, the request fails, and does not create the machine user
dp_profiler_user
required for profiling. - CDPDSS-3472: Profiler jobs are showing up twice when two data lakes are present
- Cloudera Data Catalog does not support more than one data lakes (or base clusters). Connecting two data lakes will result in all profiler jobs showing as duplicated in the Profilers page.
- CDPDSS-3395: Incorrect results are being displayed after navigation, when "owners" filter is selected
- In the Search page, when returning to the list of results after opening the Asset Details of one the results and repeating the search with the same filter, other entities belonging to owners different than the selected can appear.
- CDPDSS-3381: The Ranger Audit Profiler is showing status as FINISHED/SUCCESS even though there is error with the profilers
- The Ranger Audit Profiler can shows an incorrect status when the NameNode is stopped, and it is can get stuck in FINISHED.
- CDPDSS-3353: Profiler Configuration page is giving error, if browser's preferred language is not UK English
- The
en-gb
.
is may be incorrectly rendered if the web browser's preferred language is not
set to - CDPDSS-2688: Hive Column On-demand Profiler is failing but the Asset Details page is not updated with 'Failed State'
- A failed Hive Column On-Demand Profiler job is incorrectly not updated to Failed state in .