Known issues
This section lists known issues that you might run into while using the Data Catalog service.
- CDPDSS-213: Launching of Profilers failing for older SDX instances
- Problem: When you try to launch Profilers with older SDX instances, the launch operation fails.
- CDPDSS-144: Filter Results Count Mismatch
- Problem: When you search and filter the results using Created Before, the count displayed in the filters panel is incorrect. But, the number of search results is accurate.
- CDPDSS-144: Search icon within dataset does not work
- Problem: When you try to search for an asset within a dataset and click the search icon, it does not yield any results.
- CDPDSS-143: Edit button appears after creating a new dataset
- Problem:After creating a new dataset, when you visit the dataset, the Edit button appears instead of Add Assets.
- CDPDSS-81: When you select a table tag, owner filters along with the counts disappear.
- Problem: When you select a table tag, owner filters along with the counts disappear.
- 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-360: Sensitive and Hive Column Profilers do not support managed Hive tables.
- Problem: Profilers cannot access the storage file of the managed table.
- 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-412: Support for Data Catalog on 7.0.2 runtime SDX. In 7.0.2, Data Catalog
profiler jarsare not part of pre-warmed images of 7.0.2 runtime. - Workaround: Data Catalog users who are on 7.0.2 runtime SDX can launch profilers,
provided explicit entitlement access is granted for the location of
profiler jars. - CDPDSS-789: Adding system tag 'dp' prevents further editing of tags on the assets
- Problem: Adding system tag 'dp' prevents further editing of tags on the assets
- CDPDSS-795: Search bar in schema tab goes empty, but previous results are shown
- Problem: Search results displays previous results.
- CDPDSS-797: Schema search tab displays all results for not existing search string
- Problem: Search by terms which have no hits and returns all assets.
- CDPDSS-1055: Multiple tagging across different types throws 504 Gateway Timeout error
- Problem:504 Bad Gateway error is displayed
- CDPDSS-1075: When one specific asset is tagged to multiple tags from the search page, an incomplete alert is displayed
- Problem:Asset name display is inconsistent. Only the first tag is displayed, remaining tag messages do not display the asset name.
- 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-1154: Name of the profiler being run should be displayed with schedules
- Problem:The profiler name is being displayed on a row on opening the collapsable chart.
- CDPDSS-1179: Data Catalog search via Atlas’s /v2/search/basic API doesn’t retrieve results when the search text mentioned in the entity filter criteria (like searching by DB / table name) has special characters (like + - & | ! ( ) { } [ ] ^ ” ~ * ? :)
- Workaround:No known workaround via Data Catalog.
