Known issues
Learn about the known issues in Data Catalog, the impact or changes to the functionality, and the workaround.
Unsupported Features
Known Issues
- CDPDSS-342: Deleted table is still shown in dataset
- Problem: Created table in a dataset if deleted, does not get deleted completely and shows up in the dataset. If the same table is created again, the edit and search options are enabled. When you save the table, there are two tables displayed, thought the first instance of the same table was deleted.
- CDPDSS-362: dpprofiler.submitter.batch.size property is not taking effect
- Problem: As part of
application.confsafety valve under profiler scheduler, applying the propertydpprofiler.submitter.batch.sizeis not taking effect. It defaults to 50. - CDPDSS-1150: A job which is in running state remains in the running state, due to some scenarios (restarting workload cluster) and it gets stuck
- Problem:A running job does not get killed or timed-out after certain duration of time.
- CDPDSS-1153: Filters must be on schedules level and not on jobs
- Workaround: N/A
- CDPDSS-1375: Search enhancements by TERM
- Problem: In DataCatalog, if the term is included in the asset search query, the count of the assets next to the Data Lakes displays NA. It is because, Atlas search with Glossary term is returns approximate count as -1.
