Cloudera Docs

Known Issues in Apache Hive

Learn about the known issues in Hive, the impact or changes to the functionality, and the workaround.

Known Issues identified in Cloudera Runtime 7.3.1.500 SP3

CDPD-88865: Unicode character support with a MySQL backend
Cloudera on premises 7.3.1.500 and all base versions
When a cluster's backend is a MySQL database, CREATE TABLE statements with more than two Unicode column names can fail. This is a known bug, HIVE-18083, where the MySQL database does not support non-ASCII characters in column names.
None

Known Issues identified in Cloudera Runtime 7.3.1.400 SP2

There are no new known issues identified for Hive in this release.

Known Issues identified in Cloudera Runtime 7.3.1.300 SP1 CHF1

There are no new known issues identified for Hive in this release.

Known issues identified in Cloudera Runtime 7.3.1.200 SP 1

There are no new known issues identified for Hive in this release.

Known Issues identified in Cloudera Runtime 7.3.1.100 CHF1

The following section lists the known issues identified in this release:
CDPD-77738: Atlas hook authorization issue causing HiveCreateSysDb timeout
7.1.9 SP1 CHF4, 7.1.7 SP3 CHF7, 7.3.1.100, and its higher versions
Atlas hook authorization error causes HiveCreateSysDb command to time out due to repeated retries.
None
CDPD-78490: HiveCreateSysDb command fails
7.1.9 SP1, 7.3.1.0, and its higher versions
Hive services fail to start due to HiveCreateSysDb command failure during the first run.
None
CDPD-72605: Optimizing partition authorization in HiveMetaStore
7.3.1.200
7.3.1.0
The add_partitions() API in HiveMetaStore unnecessarily authorizes both new and existing partitions, increasing processing time and load on the authorization service.
None

Known Issues identified in Cloudera Runtime 7.3.1

CDPD-74680: DAG not retried after failure
7.3.1 and its higher versions
When executing a Hive query, if the ApplicationMaster container fails, Hive does not retry the DAG if the failure message contains some diagnostic information including a line break, leading to query failure (instead of retry).
None
HiveServer2 goes into a hung state intermittently
7.3.1 and its higher versions
HiveServer2 can intermittently hang or crash due to heap out-of-memory (OOM) errors triggered by the default 1 GB cache limit for fetch tasks. This occurs with certain queries that exceed the available heap space.
  1. Disable the fetch task caching feature by setting: hive.fetch.task.caching=false.
  2. You can adjust the hive.fetch.task.conversion.threshold property to a lower value in the megabyte range. The default value in Cloudera on premises 7.3.1 is 1 GB.