Known issues in Hive Virtual Warehouses
This topic describes the Hive Virtual Warehouse known issues for Cloudera Data Warehouse (CDW) Private Cloud.
Known issues identified in 1.5.2
No new known issues identified in 1.5.2.
Known issues identified in 1.5.1
- DWX-16891: Hive-Ranger integration issue after a refresh
- You may see the following error after you refresh a Hive Virtual Warehouse: Error while compiling statement: FAILED: HiveAccessControlException Permission denied. This happens because Hive fails to evaluate Ranger group policies when the Virtual Warehouse is updated--either by upgrading or refreshing it.
- Rebuild the Hive Virtual Warehouse to fix the Ranger integration issues.
- DWX-15480: Hive queries fail with FILE_NOT_FOUND error
- ACID directory cache may become outdated in Tez AMs in case of ACID tables that change often, possibly leading to different errors with the same root cause: "split generation works from cache pointing to non-existing files". And you may see the following error in the diagnostic bundles and query logs: FILE_NOT_FOUND: Unable to get file status.
- Disable the cache by setting the value of the
hive.txn.acid.dir.cache.durationproperty to -1 by going to from the CDW web interface.
- DWX-15287: Drop database query for Hive fails with Invalid ACL Exception
- You may see the following error in a Hue or beeline session when
running DROP DATABASE, DROP TABLE, or ALTER TABLE DROP PARTITION operations on a Hive
Virtual Warehouse that is in Stopped state:
KeeperErrorCode = InvalidACL for /llap-sasl/user-hive".The exception is caused because the Hive Virtual Warehouse tries to evict the cache in the LLAP executors, but the compute pods of the stopped warehouse are no longer running.
- Start the Virtual Warehouse before you run the DROP
DATABASE, DROP TABLE, or ALTER TABLE DROP PARTITION operations.Alternatively, you can add the
hive.llap.io.proactive.eviction.enabled=falsesetting in the
hive-site.xmlfile. This method may result in some performance degradation, because LLAP no longer discards the dropped database/table or temp table related buffers.
- Log in to CDW as DWAdmin.
- Click hive-site from the Configuration files drop-down menu. on the Virtual Warehouse tile and select
- Click and add the following
- Click Apply Changes.
Wait for the Virtual Warehouse to refresh and return to Running or Stopped state.
Known issues identified before 1.4.1
- DWX-4842: Entities are not being created in Atlas
- 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.
- Using the
keytool, convert the PKCS12 truststore in the base cluster to a JKS truststore.