Known issues in Database Catalogs

This topic describes the Database Catalog known issues for Cloudera Data Warehouse Private Cloud.

DWX-6215: Loading demo data in Database Catalogs fails

Problem: When you select the option to load demo data when creating a Database Catalog, loading the demo data fails with the following alert on the CDP Dashboard:

Workaround: Add the username of the table owner to the objects list of users/groups that can access the particular database or table associated with the demo data within Ranger. For more information about granting access with Ranger, see Using Ranger to provide authorization in CDP

DWX-6160: SHOW TABLES command or listing tables does not return expected listing of tables

Problem: If access to the databases or tables of a non-default Database Catalog is granted with the OWNER property in Ranger, then running the SHOW TABLES command or any other listing of tables in a UI like Hue does not return the expected list of tables owned by the user. This might occur even if queries run against the tables succeed.

Workaround: Add the username of the table owner to the objects list of users/groups that can access this particular database or table within Ranger. For more information about granting access with Ranger, see Using Ranger to provide authorization in CDP.

DWX-4534: Default Database Catalog fails to start when Hive metastore on base cluster does not use PostgreSQL database

In CDW Private Cloud version 1.1, you must use a PostgreSQL database for your Hive metastore on the base cluster. For more information, see Base cluster database requirements for CDW Private Cloud.

DWX-5247: Database Catalog managed tables location points to incorrect directory

Problem: Default Database Catalogs that are created with the CDW Private Cloud UI point to an incorrect directory location for managed tables.

Workaround: To correct this, perform the following steps:

Using Data Analytics Studio (DAS), run a DESCRIBE statement to check the default database MANAGEDLOCATION setting:

DESCRIBE database default;

DB_NAME   COMMENT                 LOCATION                           MANAGEDLOCATION                 more…
default   Default Hive database   hdfs://ns1/warehouse/dwx- more...  hdfs://ns1/user/hive/warehouse  more…

Note the HDFS URL because you will need it to correct the setting in Step 3.

Still using DAS, run the following query to get the correct path for the default database:
```
SET hive.metastore.warehouse.dir;

Result:
hive.metastore.warehouse.dir=/warehouse/dwx-impala7b096/warehouse-1597085504-cv4b/warehouse/tablespace/managed/hive
```
Note that this path does not include the HDFS URL that you obtained in Step 1.
A user with ALTER privileges on the default database sets the database's MANAGEDLOCATION using the following elements from previous steps:
- HDFS URL from Step 1: hdfs://ns1…
- Results returned by the SET statement used in Step 2: …/warehouse/dwx-impala7b096/warehouse-1597085504-c4b/warehouse/tablespace/managed/hive
```
ALTER DATABASE default SET MANAGEDLOCATION 'hdfs://ns1/warehouse/dwx-impala7b096/warehouse-1597085504-cv4b/warehouse/tablespace/managed/hive';
```