Known issues in Database Catalogs
This topic describes the Database Catalog known issues for Cloudera Data Warehouse Private Cloud.
Known Issues identified in 1.5.0
- DWX-14281: Configuration changes to Database Catalogs are not applied
- When you change Database Catalog configurations from the CDW UI, the changes are not applied.
- DWX-14022: The metastore-sys-init-job job fails with "Table not found 'TXNS'" error
- You see that the default Database Catalog starts successfully and the UI indicates it as running, however, the metastore-sys-init pods are in an error state. You also see that the Hive MetaStore (HMS) pods fail with the following error: "[HiveServer2-Background-Pool: Thread-125] ERROR org.apache.hadoop.hive.ql.parse.CalcitePlanner - org.apache.hadoop.hive.ql.parse.SemanticException: Line 1:1117 Table not found 'TXNS'". This happens because the TXNS table is not present on CDP Private Cloud Base version 7.1.7 SP2.
Known Issues identified in 1.4.1
- DWX-13758: Updating the pre-upgrade Database Catalog and Virtual Warehouse fails silently
- If you update or refresh the Database Catalogs and Virtual
Warehouses that were created before you upgraded to 1.4.1 by changing their
configurations, then they may go into an erroneous state.
Do not update or refresh the Database Catalogs and Virtual Warehouses that were created before you upgraded to 1.4.1.
Known Issues identified before 1.4.1
- DWX-8979: Parquet demo data set only loads partially on OpenShift clusters
- On OpenShift clusters, the Parquet demo data set loads partially on a non-default Database Catalog, intermittently. As a result, you may intermittently and partially see the demo data set in Hue.
