Cloudera Docs

Behavioral changes

Behavioral changes for Cloudera Data Warehouse service on cloud introduce functional adjustments to service layer version 1.13.1-b44, Hive, Impala, and Hue runtime version 2026.0.21.4-12, and Trino runtime version 2026.0.24.0-37.

Behavior changes in Cloudera Data Warehouse on cloud

Summary: Cloudera Data Warehouse instances now tagged at launch through CloudFormation LaunchTemplate
Previous behavior: Cloudera Data Warehouse applied environment tags to EC2 instances only after instance creation by using the aws-tagger DaemonSet. The CloudFormation Launch Templates did not include TagSpecifications, so the ec2:RunInstances API call did not carry any tags. This behavior caused Cloudera Data Warehouse environment activation to fail in AWS accounts with strict service control policies (SCP) that mandate tags at instance creation.
New behavior: Cloudera Data Warehouse environment tags, including tags inherited from the Cloudera Data Platform environment as well as Cloudera Data Warehouse specific tags such as clusterId, envId, and clusterName, are now injected directly into the TagSpecifications section of all CloudFormation Launch Template resources. As a result, tags are present on the ec2:RunInstances API call for EC2 instances, root Elastic Block Store (EBS) volumes, and primary Elastic Network Interfaces (ENI), enabling compliance with AWS SCPs that require tags at creation time. The end-state tags on resources remain identical, and no user action is required.

Behavior changes in Cloudera Data Explorer (Hue) on Cloudera Data Warehouse on cloud

There are no behavior changes in this release.

Behavior changes in Hive on Cloudera Data Warehouse on cloud

Summary: The CBO Plan attribute in EXPLAIN FORMATTED output changed from a string to a JSON object
Previous behavior:
The value of the CBO Plan attribute in the JSON result of an EXPLAIN FORMATTED statement was a plain, escaped string.
New behavior:
The value of the CBO Plan attribute is now a fully formed JSON object instead of a plain string. In most cases, this change does not affect your workflow. If you parse the JSON content inside the CBO Plan attribute, update your parsing logic to account for the new format.

Apache Jira: HIVE-29357

Behavior changes in Iceberg on Cloudera Data Warehouse on cloud

There are no behavior changes in this release.

Behavior changes in Impala on Cloudera Data Warehouse on cloud

Summary: Impala now checks your permissions before reading the URL set in the avro.schema.url table property.
Previous behavior: When you created a table with the avro.schema.url property pointing to an HTTP or file URL, Impala read that URL without checking your permissions. If the URL did not contain a valid Avro schema, its content could appear in the error message.
New behavior: Impala checks whether you have permission to read the URL set in avro.schema.url before reading it. If you do not have permission, the table creation fails. Error messages no longer display the URL content. After you upgrade, ensure that users who create tables with this property have read permission on the URL in Ranger.

Behavior changes in Trino on Cloudera Data Warehouse on cloud

Summary: Removal of dynamic filtering properties
Previous behavior: Dynamic filtering configuration relied on the enable-large-dynamic-filters configuration property and its corresponding enable_large_dynamic_filters system session property. Additionally, configuration relied on the dynamic-filtering.small* and dynamic-filtering.large-broadcast* configuration property families.
New behavior: The enable-large-dynamic-filters configuration property, the enable_large_dynamic_filters system session property, and the dynamic-filtering.small* and dynamic-filtering.large-broadcast* configuration properties are removed. You must configure dynamic filtering by using the following new properties:
  • dynamic-filtering.max-distinct-values-per-driver
  • dynamic-filtering.max-size-per-driver
  • dynamic-filtering.range-row-limit-per-driver
  • dynamic-filtering.partitioned.max-distinct-values-per-driver
  • dynamic-filtering.partitioned.max-size-per-driver
  • dynamic-filtering.partitioned.range-row-limit-per-driver
  • dynamic-filtering.max-size-per-operator
  • dynamic-filtering.max-size-per-filter
  • dynamic-filtering.partitioned.max-size-per-operator

The following legacy configuration properties map to the updated property names:

Table 1. Dynamic filtering property mapping
Removed legacy property New driver-level replacement
dynamic-filtering.large.max-distinct-values-per-driver dynamic-filtering.max-distinct-values-per-driver
dynamic-filtering.large.max-size-per-driver dynamic-filtering.max-size-per-driver
dynamic-filtering.large.range-row-limit-per-driver dynamic-filtering.range-row-limit-per-driver
dynamic-filtering.large.max-size-per-operator dynamic-filtering.max-size-per-operator
dynamic-filtering.large.max-size-per-filter dynamic-filtering.max-size-per-filter
dynamic-filtering.large-partitioned.max-distinct-values-per-driver dynamic-filtering.partitioned.max-distinct-values-per-driver
dynamic-filtering.large-partitioned.max-size-per-driver dynamic-filtering.partitioned.max-size-per-driver
dynamic-filtering.large-partitioned.range-row-limit-per-driver dynamic-filtering.partitioned.range-row-limit-per-driver
dynamic-filtering.large-partitioned.max-size-per-operator dynamic-filtering.partitioned.max-size-per-operator

The following experimental and legacy configuration properties are removed:

  • experimental.enable-dynamic-filtering
  • experimental.dynamic-filtering-max-per-driver-row-count
  • experimental.dynamic-filtering-max-per-driver-size
  • experimental.dynamic-filtering-refresh-interval
  • dynamic-filtering-max-per-driver-row-count
  • dynamic-filtering-max-per-driver-size
  • dynamic-filtering-range-row-limit-per-driver
  • dynamic-filtering.service-thread-count
  • enable-coordinator-dynamic-filters-distribution