Known issues in Hive Virtual Warehouses

This topic describes the Hive Virtual Warehouse known issues for Cloudera Data Warehouse (CDW) Private Cloud.

DWX-8540: Concurrent Hive queries fail on an air-gapped cluster
Problem: Concurrent Hive queries may fail on an air-gapped cluster with the following exception: “RuntimeException: java.io.IOException: Could not start Sequence Counter” due to Kerberos authentication failure.
Workaround: None.
DWX-8524: Hive queries on sys.db tables may fail
Problem: When you run queries on the sys.db table from Data Analytics Studio, you may see the following error: “Cannot create PoolableConnectionFactory (Could not open SSL root certificate file /mnt/config/current/hms-root.crt.)” on a default Database Catalog using PostgreSQL database. This happens because PostgreSQL requires SSL. This issue does not occur on Database Catalogs using MariaDB.
Workaround: None.
DWX-8500: Toggling the auto-suspend option restarts all the pods on Hive Virtual Warehouses
Problem: Both Database Catalog and service pods restart when you enable or disable the auto-suspend button for Hive Virtual Warehouses, instead of restarting only the Database Catalog pods.
Workaround: None.
DWX-7625: Hive queries fail with a “KubernetesClientException” error when services become idle
Problem: By default, a Virtual Warehouse is set to auto-suspend itself to release resources when there are no workloads running. You may see the following error in the HiveServer2 logs after you run a Hive query when the Virtual Warehouse is in an idle state: “message": "Error while compiling statement: FAILED: Hive Internal Error: org.apache.hadoop.hive.ql.metadata.HiveException(Error while invoking PreHook. hooks: io.fabric8.kubernetes.client.KubernetesClientException”.
Workaround: Restart the Virtual Warehouse by clicking Start. Alternatively, you can recreate the Hive Virtual Warehouse with the auto-suspend option disabled.
DWX-7574: Queries fail in Hive Virtual Warehouse with a RuntimeException error
Problem: Hive queries that you run from Hue and Data Analytics Studio (DAS) may fail with the following exception: “Error while compiling statement: FAILED: RuntimeException Unable to instantiate org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient'' because Hive cannot renew Kerberos tickets due to a known bug.
Workaround: As an immediate solution, restart the Virtual Warehouse by clicking Start. For a longer term fix, you can do the following:
  • Increase the value of the max_life property in the /etc/krb5kdc.conf configuration file on the base cluster Kerberos Distribution Center (KDC) server before activating the environment and then restart the KDC server.
  • Increase the value of the ticket_lifetime property to 7 days on the /etc/krb5.conf client config present on each host. The default ticket lifetime is 24 hours. Make sure that the Kerberos ticket lifetime is greater than the renewal time. For example:
    [libdefaults]
        ticket_lifetime = 1440m
        renew_lifetime = 100m

These configurations are propagated at the environment level when the Kubernetes pod is started.

DWX-6234: WAIT TIME seconds cannot be set to "0" in the Hive Virtual Warehouse UI
Problem: The slider that can be used to set WAIT TIME in the Hive Virtual Warehouse UI displays a range from 0 to 1000, but if you set it to 0, the UI automatically changes it to 60.
Workaround: None.
DWX-6163: SHOW TABLES command does not produce a list of tables that are owned by the current user
Problem: When you run the SHOW TABLES command against a Hive Virtual Warehouse, tables are only returned if you have explicit read or read/write access to the table, or if you belong to a group that has read or read/write access. If you only have access to the tables because you are the owner of the objects, you can query the table content, but the table names do not appear in the SHOW TABLES command output.
Workaround: Add the owner of the database or the tables as a user with read or read/write access to the tables directly.
DWX-6132: Hive Virtual Warehouses require Cloudera Manager 7.2.4 and CDP 7.1.5
Problem: In CDW Private Cloud 1.1, Hive Virtual Warehouses might get stuck in the starting state.
Workaround: To ensure that Hive Virtual Warehouses work as expected in CDW Private Cloud 1.1, make sure that you are using Cloudera Manager 7.2.4 and CDP 7.1.5.
DWX-4703: Using UDFs and custom JARs are not supported
Problem: In the 1.1 release of Cloudera Data Warehouse Private Cloud, using UDFs and custom JARs are not supported on Hive Virtual Warehouses.
Workaround: None.
DWX-4842: Entities are not being created in Atlas
Problem: Base clusters that are using Java 11 might be using truststores in PKCS12 format. Currently, Hive Virtual Warehouses on CDW Private Cloud only supports truststores in JKS format. This prevents the entities from being created in Atlas.
Workaround: Using the keytool, convert the PKCS12 truststore in the base cluster to a JKS truststore.