February 3, 2025 - Hotfix

Review the new features introduced in this release of Cloudera Data Warehouse service on Cloudera on cloud

• Cloudera Data Warehouse on Azure environments
• Cloudera Data Warehouse on AWS environments

Review the fixed issues in this release of the Cloudera Data Warehouse service on cloud

DWX-20070: Incompatibility with custom subdomains using .dw format

Cloudera Data Warehouse environments could not be activated when specifying a custom subdomain in the older .dw format using the --custom-subdomain CLI flag. This resulted in certificate creation failures with the error:

error while obtaining certificate: context canceled Error Code: undefined

This issue impacted customers with the entitlement CDW_CUSTOM_CLUSTER_ID using the old .dw domain format.

The fix includes updating the certificate creation process to support custom subdomains in the old .dw format. Cloudera Data Warehouse environments can now be activated seamlessly with custom subdomains in both legacy and updated formats however, Cloudera strongly recommends to migrate to the new format that was introduced in August, 2021, see Cloudera Data Warehouse on cloud endpoints change.

Review the known issues in this release of the Cloudera Data Warehouse on cloud service.

Database Catalog fails to start after upgrading Data Lake to Azure Flexible Server

After you upgrade your Data Lake from Azure Single Server to Azure Flexible Server, the Cloudera Data Warehouse Database Catalog fails to start.

To address this issue, reactivate the Cloudera Data Warehouse environment based on the following choices:

• If the environment is essential and needs to be retained, you can use the Cloudera Data Warehouse Backup and Restore feature. The backup and restore process saves your environment parameters, making it possible to recreate your environment with the same settings, URL, and connection strings you used in your previous environment.
• If the environment is expendable, you can choose to deactivate and reactivate the enviornment.

Database Catalog goes to an error state after a Data Lake resize

After a Cloudera Data Lake resize, the Cloudera Data Warehouse Database Catalog needs to be restarted to consider the change in Data Lake configuration. You can restart the Database Catalog using the CDP CLI or by using the Stop and Start functionality from the Cloudera Data Warehouse UI. However, irrespective of how the Database Catalog is restarted, it ends up in an "Error" state.

After you resize the Cloudera Data Lake, start the Database Catalog from the Cloudera Data Warehouse UI and then rebuild it.

You must also ensure that you restart each Virtual Warehouse as recommended in Data Lake resizing post-requisites.

CDPD-75422: Impala schema case sensitivity issue with workaround

Impala's schema is case insensitive, causing errors with mixed case schema elements created through Spark during predicate pushdown.

• Create tables through Impala to ensure lower case schema.
• Avoid upper case in Spark: Do not use upper case when creating tables through Spark.
• Fix existing tables: Use ALTER TABLE to rename upper case columns:

  ALTER TABLE `database`.`iceberg_table` CHANGE COLUMN ID id string;

Unable to resize Workload Aware Autoscaling enabled Impala Virtual Warehouse using the UI

If you are using the Cloudera Data Warehouse UI to resize an Impala Virtual Warehouse that is enabled for Workload Aware Autoscaling, you may notice a message in the Sizing and Scaling tab of the Virtual Warehouse Details page — "Some operations are still running. Please wait...", and you are unable to proceed further although the Virtual Warehouse is in a healthy state.

To address this issue, you can resize your Virtual Warehouse using the cdp dw update-vw CDP CLI command. For more information, see the CDP CLI documentation.