Known Issues in Apache Hive
Learn about the known issues in Hive, the impact or changes to the functionality, and the workaround.
- TSB-732 2024: Incorrect results are generated by Hive JOIN when bloom filter is activated
- The bloom filter implemented in HIVE-23880 was designed to enhance performance for queries with JOIN statements, where one small table and another significantly larger table is joined on partition keys. However, the bloom filter introduced an issue in Apache Hive (Hive), when dynamic semijoin redaction is involved that generates incorrect query results. This issue is corrected in HIVE-26655.
- Upstream JIRA
- Hive-23880(cause)HIVE-26655(fix)
- Knowledge article
- For the latest update on this issue see the corresponding Knowledge article: TSB 2024-732: Incorrect results are generated by Hive JOIN when bloom filter is activated
- CDPD-66549: Cloudera Machine Learning failed to connect to Hive Metastore during an upgrade
- Hive Metastore (HMS) becomes unreachable during and after an
upgrade from Cloudera Runtime 7.2.17 to higher versions.
Clients communicate with HMS using delegation tokens and these tokens that are required during a connection, is stored in memory. After an upgrade, all issued tokens are lost when the HMS restarts, and as a result the handshake communication using the old token is unsuccessful. If you set the HMS Delegtaion Token Store to DBTokenStore, HMS will persist the tokens in the backend database. The tokens can then be retrieved after an upgrade since it is stored ensuring that the handshake communication using the old token is successful.
- CDPD-54988: Disallow creation of Temporary Hive Iceberg tables
- Atlas by default skips ingesting temporary tables created in Hive. But when searched for the newly created temporary Hive tables, it displays them in the search results.
- CDPD-15518: ACID tables you write using the Hive Warehouse Connector cannot be read from an Impala virtual warehouse.
- Read the tables from a Hive virtual warehouse or using Impala queries in Data Hub.
- CDPD-13636: Hive job fails with OutOfMemory exception in the Azure DE cluster
- Set the parameter hive.optimize.sort.dynamic.partition.threshold=0. Add this parameter in Cloudera Manager (Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml)
- ENGESC-2214: Hiveserver2 and HMS service logs are not deleted
- Update Hive log4j configurations. Hive -> Configuration -> HiveServer2 Logging Advanced Configuration Snippet (Safety Valve) Hive Metastore -> Configuration -> Hive Metastore Server Logging Advanced Configuration Snippet (Safety Valve) Add the following to the configurations: appender.DRFA.strategy.action.type=DELETE appender.DRFA.strategy.action.basepath=${log.dir} appender.DRFA.strategy.action.maxdepth=1 appender.DRFA.strategy.action.PathConditions.glob=${log.file}.* appender.DRFA.strategy.action.PathConditions.type=IfFileName appender.DRFA.strategy.action.PathConditions.nestedConditions.type=IfAccumulatedFileCount appender.DRFA.strategy.action.PathConditions.nestedConditions.exceeds=same value as appender.DRFA.strategy.max
- CDPD-10848: HiveServer Web UI displays incorrect data
- If you enabled auto-TLS for TLS encryption, the HiveServer2 Web UI does not display the correct data in the following tables: Active Sessions, Open Queries, Last Max n Closed Queries
- CDPD-11890: Hive on Tez cannot run certain queries on tables stored in encryption zones
- This problem occurs when the Hadoop Key Management Server (KMS) connection is SSL-encrypted and a self signed certificate is used. SSLHandshakeException might appear in Hive logs.
