What's new

Review the new features introduced in this release of Cloudera Data Warehouse on cloud, version 1.13.1-b44 .

What's new in Cloudera Data Warehouse on cloud

Azure AKS 1.35 upgrade: Cloudera supports the Azure Kubernetes Service (AKS) version 1.35. In 1.13.1-b44 (released September 18, 2026), when you activate an Environment, Cloudera Data Warehouse automatically provisions AKS 1.35. To upgrade to AKS 1.35 from a lower version of Cloudera Data Warehouse, you must backup and restore Cloudera Data Warehouse.
note
Using the Azure CLI or Azure portal to upgrade the AKS cluster is not supported and might result in cluster instability or downtime. For more information about upgrading, see Upgrading an Azure Kubernetes Service (AKS) cluster.
AWS EKS 1.35 upgrade: Cloudera supports the AWS Elastic Kubernetes Service (EKS) version 1.35. In 1.13.1-b44 (released September 18, 2026), when you activate an Environment, Cloudera Data Warehouse automatically provisions EKS 1.35. To upgrade to EKS 1.35 from a lower version of Cloudera Data Warehouse, you must backup and restore Cloudera Data Warehouse.
note
Using the AWS tools to upgrade the EKS cluster is not supported and might result in cluster instability or downtime. For more information about upgrading, see Upgrading an Amazon Kubernetes Service (EKS) cluster.
Configuring Intermediate Results Cache in Impala Virtual Warehouses: Cloudera Data Warehouse supports the Intermediate Results Cache feature for Impala Virtual Warehouses to improve query performance and resource efficiency for repeated analytic workloads. You can now enable and configure the cache during Impala Virtual Warehouse creation or update an existing Impala Virtual Warehouse. When enabled, a default cache size of 20 GiB is applied if not specified. Configured values must be greater than 0 and cannot exceed 50% of the data cache; invalid values are rejected during validation. For more information, see Configuring Intermediate Results Cache for Impala Virtual Warehouse.
Updated default Azure VM instance types for Virtual Warehouses and shared services: The default Azure VM instance types for Cloudera Data Warehouse are updated to align with Microsoft Azure's deprecation of v1–v4 VM series.The deprecated Standard_E16_v3 and Standard_E16ds_v4 instance types are no longer available for selection as compute instance types. Additionally, the shared services instance type has changed from Standard_D8s_v3 to Standard_D8ds_v5. This update ensures continued scalability and prevents deployment or quota limitations ahead of Azure capacity growth restrictions effective 31 July 2026. For more information, see Compute Instance Types for Cloudera Data Warehouse.
Support for EKS API_AND_CONFIG_MAP authentication mode on AWS: Newly activated Amazon EKS clusters in Cloudera Data Warehouse on cloud now use the API_AND_CONFIG_MAP authentication mode. This update adds support for AWS EKS access entries while maintaining complete backward compatibility with the existing aws-auth ConfigMap authentication mechanism. Aligning with AWS recommended cluster access management controls, this change transitions environments toward API-based access without impacting existing cluster operations.
Cloudera Data Visualization updated to version 8.1.4: The Cloudera Data Visualization component included in Cloudera Data Warehouse is updated to version 8.1.4.1000-4. This update brings the latest improvements, bug fixes, and enhancements from the Cloudera Data Visualization 8.1.4 release to Cloudera Data Warehouse, including a refreshed look across the product with updated colors, fonts, borders, and spacing.

What's new in Cloudera Data Explorer (Hue) on Cloudera Data Warehouse on cloud

Enhanced session security for Cloudera Data Explorer (Hue): Data Explorer now includes security for the session ID (sessionid) cookie. This enhancement helps prevent unauthorized access results in data exposure, unauthorized query execution, and job submission across connected Data Explorer services.; For more information, see Securing sessions .

What's new in Hive on Cloudera Data Warehouse on cloud

Choose the materialization strategy for common table expressions: You can now choose how Hive materializes a common table expression (CTE). The new hive.optimize.cte.suggester.type property lets you select the syntax-based strategy, the cost-based strategy, or disable CTE materialization, so the two strategies no longer interfere with each other and cause excessive materialization. This property defaults to AST, which preserves existing behavior.
Apache Jira: HIVE-29217

What's new in Iceberg on Cloudera Data Warehouse on cloud

Z-ordering support for Iceberg tables from Hive: Hive supports Z-ordering for Iceberg tables in CREATE TABLE and INSERT statements. Specify Z-order columns with WRITE [LOCALLY] ORDERED BY ZORDER when you create a table. Hive applies the same Z-order layout when you insert data into that table.; For more information, see Z-ordering feature.
Apache Jira: HIVE-29133
CREATE TABLE LIKE for Iceberg from non-Iceberg tables in Impala: Impala supports using CREATE TABLE LIKE with STORED BY ICEBERG to create an Iceberg table from an existing non-Iceberg table in the metastore, such as Parquet, ORC, Avro, or Text. The operation copies the source schema into Iceberg table metadata only. Use INSERT INTO to load data.; For more information, see Create an Iceberg table from a non-Iceberg table (Impala).
Apache Jira: IMPALA-13299

What's new in Impala on Cloudera Data Warehouse on cloud

There are no new features in this release.

What's new in Trino on Cloudera Data Warehouse on cloud

Configuring query-level fault tolerance and coordinator high availability for Trino: Cloudera Data Warehouse supports fault tolerance with query-level retry and Active-Passive coordinator high availability (HA) for Trino Virtual Warehouses. Query-level retry automatically reruns failed queries up to four times using in-memory buffer spooling, while Active-Passive HA deploys a standby coordinator to quickly take over if the active coordinator crashes or shuts down, ensuring continuous cluster availability. You can enable and configure both settings when creating or editing a Trino Virtual Warehouse in the Cloudera Data Warehouse web UI. For more information, see Configuring query-level fault tolerance for Trino.
Trino runtime upgraded: The Trino runtime is upgraded from version 479 to 481.; This upgrade introduces stability improvements and performance optimizations.
Apache Kudu connector available in federation connectors: Trino supports the Apache Kudu connector as part of the federation connectors. You can query, insert, and delete data directly in Apache Kudu using Trino. See Apache Kudu connector support for Trino
Connection pooling for Hive and Impala federation connectors: Cloudera Data Warehouse now supports JDBC connection pooling for the Hive-jdbc and Impala federation connectors, extending the pooling already available for the MySQL, PostgreSQL, MariaDB, Teradata, and Oracle connectors. When pooling is enabled, a connector reuses physical JDBC connections instead of opening and closing one for every query, which reduces connection handshake latency and load on the target data source. Connection pooling is disabled by default; to enable it, set connection-pool.enabled to true in the connector configuration.
Kerberos authentication for the Trino Oracle connector: The Trino Oracle connector now supports Kerberos authentication, so you can connect Trino to Kerberos-secured Oracle databases. For more information, see Configuring Kerberos authentication for the Oracle connector