Known issues in Hive Virtual Warehouses on public clouds
Learn about the known issues related to Hive Virtual Warehouse in Cloudera Data Warehouse (CDW) service on public clouds, the impact or changes to the functionality, and the workaround.
- DWX-10271: Missing log section in Hive query results
- In a Hive Virtual Warehouse, when you run a query in Hue, the query results do not contain a logs section.
- DWX-8118: INSERT INTO command fails under certain circumstances
- This problem affects users who have a PostgreSQL database as the backend Hive database. If
you create a table A and create a table B as select (CTAS) from an empty table A,
inserting values into table B fails as follows:
Error while compiling statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.StatsTask.org.apache.thrift.transport.TTransportException
- DWX-5841: Virtual Warehouse endpoints are now restricted to TLS 1.2
- Problem: TLS 1.0 and 1.1 are no longer considered secure, so now Virtual Warehouse
endpoints must be secured with TLS 1.2 or later, and then the environment that the Virtual
Warehouse uses must be reactivated in CDW. This includes both Hive and Impala Virtual
Warehouses. To reactivate the environment in the CDW UI:
- Deactivate the environment. See Deactivating AWS environments or Deactivating Azure environments.
- Activate the environment. See Activating AWS environments or Activating Azure environments
- DWX-5926: Cloning an existing Hive Virtual Warehouse fails
- Problem: If you have an existing Hive Virtual Warehouse that you clone by selecting Clone from the drop-down menu, the cloning process fails. This does not apply to creating a new Hive Virtual Warehouse.
- DWX-2690: Older versions of Beeline return SSLPeerUnverifiedException when submitting a query
-
Problem: When submitting queries to Virtual Warehouses that use Hive, older Beeline clients return an SSLPeerUnverifiedException error:
javax.net.ssl.SSLPeerUnverifiedException: Host name ‘ec2-18-219-32-183.us-east-2.compute.amazonaws.com’ does not match the certificate subject provided by the peer (CN=*.env-c25dsw.dwx.cloudera.site) (state=08S01,code=0)
Technical Service Bulletins
- TSB 2021-525: Hive Virtual Warehouse in Cloudera Data Warehouse (CDW) available in CDP Public Cloud does not start the required nodes and further does not scale up/down
- When Hive Virtual Warehouse is configured to start with a minimum scaling factor > 1, there is a chance that it will not start the required number of nodes. When this happens it will fail to release the nodes when stopped and result in an increase in cost. The scale up does not work too.
Symptoms:
- When Virtual Warehouse moves to started state, the UI will show as started but the number of instances started is less than what was configured.
- The Virtual Warehouse will not scale up at all, it will be stuck at the initial number of nodes.
- Further, when the cluster reaches “stopped” state either manually or via configured idle timeout, the UI will show the state as stopped but the nodes are not actually released.
- Knowledge article
- For the latest update on this issue see the corresponding Knowledge article: TSB 2021-525: Hive Virtual Warehouse in Cloudera Data Warehouse (CDW) available in CDP Public Cloud does not start the required nodes and further does not scale up/down