Cloudera Docs

Behavioral changes in Cloudera Data Warehouse on premises 1.5.5 SP4

This release of the Cloudera Data Warehouse on premises is supported for service layer version 1.13.0-b81, Hive, Impala, and Hue runtime version 2026.0.21.5-18, and Trino runtime version 2026.0.24.1-10, and includes the following behavior changes.

Behavioral changes in Cloudera Data Warehouse on premises

There are no behavior changes in this release.

Behavioral changes in Cloudera Data Explorer (Hue) on Cloudera Data Warehouse on premises

Summary:Removal of automatic VACUUM from manual cleanup API
Before this release:
Previously, the Query Processor manual cleanup API (/cleanup/{startTime}) automatically ran VACUUM after deleting records. This behavior caused compatibility issues with MySQL, unexpected resource consumption, and database locks during disk space recovery.
After this release:
The manual cleanup API no longer runs VACUUM automatically after deleting records. Database administrators must run VACUUM manually when necessary.

Behavioral changes in Hive on Cloudera Data Warehouse on premises

There are no behavior changes in this release.

Behavioral changes in Iceberg on Cloudera Data Warehouse on premises

There are no behavior changes in this release.

Behavioral changes in Impala on Cloudera Data Warehouse on premises

Summary: Adding a catch-up mode to EventProcessor
Before this release:Previously, when Hive Metastore (HMS) event processing experienced a large lag or during a catalogd High Availability (HA) failover, the EventProcessor component performed full table reloads for table-level events. This could cause slow recovery times when processing large event backlogs.
After this release:Added a configurable catch-up mode by using the hms_event_catchup_threshold_s property for HMS event processing. This mode invalidates tables instead of performing expensive reloads when the event lag exceeds a configurable threshold, which improves recovery from large event backlogs.

Apache Jira: IMPALA-14230

Behavioral changes in Trino on Cloudera Data Warehouse on premises

Summary: Removal of dynamic filtering properties
Before this release: Dynamic filtering configuration relied on the enable-large-dynamic-filters configuration property and its corresponding system session property enable_large_dynamic_filters. Additionally, configuration relied on the dynamic-filtering.small* and dynamic-filtering.large-broadcast* configuration property families.
After this release: 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:

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