Cloudera Docs

Fixed issues

Review the issues fixed in this hotfix release of the Cloudera Data Warehouse (CDW) service on CDP Public Cloud.

DWX-19003: Unable to set t-shirt size for a Cloudera Data Visualization instance
You could not set or configure a t-shirt size for a Cloudera Data Visualization instance while creating or editing it from CDW. By default, any Cloudera Data Visualization instance created in CDW release version 1.9.1 used the small t-shirt size. This issue has been resolved.
DWX-19034: Unable to create an Impala Virtual Warehouse with HA enabled on older runtime versions
Enabling HA on Impala Virtual Warehouses on runtime versions lower than 2024.0.18.0-206 caused errors such as the following on the catalogd pods:
I0805 13:33:15.674875     1 thrift-util.cc:198] TSocket::open() getaddrinfo() <Host: statestored-0 Port: 24000>Name or service not known       
I0805 13:33:15.674933     1 thrift-client.cc:82] Couldn't open transport for statestored-0:24000 (Could not resolve host for client socket.)
This was because enabling HA on an Impala Virtual Warehouse enabled Statestore HA, too. Statestore HA is available starting with runtime 2024.0.18.0-206. This issue has been resolved.
DWX-19035: Service discovery does not work with Impala HA
If you created an Impala Virtual Warehouse with HA enabled in CDW 1.9.1-b233, and then tried to link to it from Cloudera Data Visualization, you could not view the required Virtual Warehouse on the Create New Data Connection modal. This issue has been resolved.
IMPALA-13270: Addressing IllegalStateException in Complex Views post upgrade
When executing queries that generate runtime filters where the same column identifier appears repeatedly after upgrading to the 2024.0.18.0-206 runtime, you encountered the following error: IllegalStateException: null. This issue has been fixed.
IMPALA-13272: Stability Improvement for analytic functions on collections
The sorting process incorrectly included unnecessary elements, causing errors during array operations and leading to frequent query failures. This issue has been fixed to ensure only complete data entries are used in the sorting process. This prevents crashes and maintains stable execution of analytic functions on collections.