Cloudera Docs

Fixed issues

Review the fixed issues in the latest Cloudera Data Warehouse on cloud, supported by version 1.12.4-b57 of the service layer and runtime version 2025.0.21.2-9.

Fixed issues in Cloudera Data Warehouse on cloud

DWX-22740: Global Admission Controller option incorrectly displayed for unsupported Impala Virtual Warehouse configurations
Previously, in Cloudera Data Warehouse, the Enable Global Admission Controller option was incorrectly displayed on the Virtual Warehouse Details page for Impala Virtual Warehouses where the High Availability (HA) field was set to Enabled (Active-Passive) or Disabled. Enabling the Global Admission Controller in these configurations resulted in an invalid request error, as it is only available for the Enabled (Active-Active) configuration.

This issue is now resolved and the Enable Global Admission Controller option is available only for the Enabled (Active-Active) configuration.

DWX-20271: Logging and metering images contain unnecessary utilities and plugins
Previously, the logging and metering functions were combined into a single image that included deprecated plugins and extra software utilities.

This issue is resolved by separating these functions into dedicated, streamlined images built on a hardened, minimal base.

DWX-14145: Hive scratch directories in Cloudera Data Warehouse on cloud not getting cleaned up
Previously, in HiveServer2, leftover scratch directories in Cloudera Data Warehouse were not automatically removed periodically or after restarts caused by unexpected shutdowns, such as an OOMKill. These leftover directories accumulated over time, consuming significant storage.

This issue is fixed by enabling the hive.start.cleanup.scratchdir=true and hive.server2.clear.dangling.scratchdir=true configurations in the Hiveserver2 hive-site.xml for Cloudera Data Warehouse deployments.

DWX-23288: Cloudera Data Warehouse on cloud environment activation failing during restore
Previously, the skipValidation field in the backend caused inconsistent behavior because it could not be controlled through the UI or v3 API. This led to situations where pre-check validations would run and, if they failed, would stop the activation or restoration of Cloudera Data Warehouse environments. This prevented the successful deployment of environments.

This issue is fixed by removing the skipValidation field from the backend. Now, pre-check validations always run, but they no longer stop the environment activation process if they fail. Instead, any validation errors are recorded as warnings in the logs, allowing the environment creation or restoration to finish without being blocked.

DWX-22546: AWS EFS data and persistent volumes not deleted after Virtual Warehouse removal
In Cloudera Data Warehouse on AWS, deleting a Virtual Warehouse did not remove associated data from the EFS volume. This occurred because the deleteAccessPointRootDir flag was disabled by default, retaining data despite the deletion policy. Additionally, missing permissions caused persistent volumes to get stuck in a Terminating state, accumulating unused resources.

This issue is now resolved.

Fixed issues in Hive on Cloudera Data Warehouse on cloud

There are no fixed issues in this release.

Fixed issues in Cloudera Data Explorer (Hue) on Cloudera Data Warehouse on cloud

CDPD-101177: File upload failure to S3 in Data Explorer (Hue)
Previously, file uploads to AWS S3 through Data Explorer (Hue) might fail in both RAZ and non-RAZ environments because the storage connector incorrectly attempted to use a legacy configuration path. This issue is resolved by ensuring the storage connector uses the correct configuration path for the boto3 SDK.
CDPD-98620: Intermittent 403 authentication failures on ABFS file uploads
Previously, an intermittent file upload failed with a 403 Client Error when uploading to ABFS. This issue occurred because the system incorrectly normalized the full URL, including the security token. This process collapsed double slashes in the signature part of the token into a single slash, causing Azure to reject the request.
This issue is now resolved by splitting the URL to ensure normalization only applies to the path component while preserving the security token signature.
CDPD-101348: Download logs button in Data Explorer (Hue) administration UI leads to incorrect URL
Previously, the Download logs button in the Data Explorer (Hue) administration UI pointed to an incorrect or outdated URL, which prevented from downloading server logs. This issue is now resolved by updating the log download API endpoints.
CDPD-101746: Performance degradation when listing many files/folders in S3
Previously, the S3 file browser became slow or unresponsive when you listed a large number of files or folders. The directory listing process triggered redundant API requests for each file, causing significant delays. This issue is now resolved by optimizing the directory listing process to retrieve file information more efficiently.
DWX-23315: Error when accessing the Impala tab in the Jobs browser
Previously, an error occurred when you clicked a query ID in the editor to open the query profile page if your environment uses an active-passive coordinator setup. This issue exists as a following changes made to support active-active coordinator configurations, preventing access to detailed query metrics in active-passive environments. This issue is now resolved.

Fixed issues in Impala on Cloudera Data Warehouse on cloud

There are no fixed issues in this release.

Fixed issues in Iceberg on Cloudera Data Warehouse on cloud

DWX-23294: Changes to hive.iceberg.allow.datafiles.in.table.location.only from DWX UI are not applied
This fix resolves an issue where updates to the hive.iceberg.allow.datafiles.in.table.location.only configuration from the DWX UI were not applied and reverted to the default value after the Virtual Warehouse restart. This fix ensures that the configuration changes made through the UI are correctly persisted and reflected in the HiveServer2 settings.

Fixed issues in Trino on Cloudera Data Warehouse on cloud

DWX-23199: Trino support restricted by environment version limitations
Previously, Trino Virtual Warehouses in Cloudera Data Warehouse environments created prior to release 1.12.1 would enter a Bad Health state with the error, service is not ready (cause: keda scaler not found). This issue restricted Trino support and autoscaling functionality in older environments.

To fix this, if you upgrade to version 1.12.1 or 1.12.2, you must delete your existing Trino Virtual Warehouses and create new ones. Starting with version 1.12.4, this requirement is removed; any Trino Virtual Warehouses created in version 1.12.1 or 1.12.2 will continue to work automatically after the upgrade.

DWX-22079: Improved Trino Virtual Warehouse restoration
Previously, restoring a Trino Virtual Warehouse only recovered the Virtual Warehouse configuration object leaving out connectors, connector associations, and secret associations. This resulted in restored Trino Virtual Warehouses without the necessary connectivity to data sources.

This issue is now resolved. The restoration process now includes individual connectors and their associations.

DWX-23203: Incorrect minimum Cloudera Data Warehouse on cloud version to support Trino auto-suspend and auto-scaling on Azure
Previously, in Cloudera Data Warehouse on Azure, the system incorrectly identified the minimum Cloudera Data Warehouse version required to support Trino Auto-suspend and Auto-scaling. These features rely on Kubernetes Event-driven Autoscaling (KEDA), which is included in Azure environments since version 1.12.1. However, the system configuration did not correctly reflect this requirement, allowing the Trino Auto-suspend option to be enabled during the creation of Trino Virtual Warehouses in Azure environments running versions 1.11.3 or 1.11.4, where KEDA was not present to manage the scaling events.

This issue is now resolved by correcting the version validation logic. The Trino Auto-suspend and Auto-scaling options are now only available for Azure environments running Cloudera Data Warehouse version 1.12.1 or later, ensuring the necessary KEDA components are present to support these features.

DWX-22133: Inconsistent auto-suspend behavior between manual and automatic Trino Virtual Warehouse start
Previously, when a suspended Trino Virtual Warehouse was started manually through the Start button, auto-suspend would trigger after one minute of inactivity. However, if it was started automatically by a query, it would only suspend after five minutes. This occurred because KEDA was paused during the manual start workflow and un-paused one minute after worker pods restarted, triggering an immediate suspend check without awareness of the start event.

This issue is resolved. The manual start workflow is corrected to align with the standard five-minute auto-suspend window.

DWX-22514: Trino Virtual Warehouse remains locked for one minute after manual operations
Previously, after manually starting or updating a Trino Virtual Warehouse, the system stayed locked for an extra minute. Attempting to perform another action during this time resulted in an error message:
Compute entity is currently ‘leased’ by another internal operation.

This issue is now resolved.

DWX-22218: Missing instanceType and imageVersion fields in Trino dw describe-vw response
Previously, the JSON response for the dw describe-vw CDP CLI command did not include the instanceType and imageVersion fields for Trino Virtual Warehouses. This prevented operational scripts from confirming the exact instance type or image version deployed on Trino Virtual Warehouses.

This issue is now resolved.

DWX-22197: Trino Virtual Warehouse dw describe-vw command missing imageVersion field
Previously, the dw describe-vw CDP CLI command for Trino Virtual Warehouses returned a JSON response that did not include the imageVersion field under the vw object. This made it difficult to identify the exact software image version through the CDP CLI.

This issue is now resolved, and the imageVersion attribute is now included in the dw describe-vw output for Trino Virtual Warehouses.

DWX-22392: Trino compute update fails due to entity being leased by a background operation
Previously, Trino auto-suspend and auto-scaling processes did not account for manual operations performed by users, such as Start or Update. To prevent conflicts between manual and automatic operations, a 1-minute delay was introduced, during which the lease of the Trino Virtual Warehouse is held after a manual operation is executed. During this delay, attempting another manual operation might result in the error message: 
Compute entity is currently 'leased' by another internal operation.

This issue is now resolved.