Behavior changes

Behavior changes in Cloudera Data Warehouse

Summary: Unified Analytics Virtual Warehouse creation and upgrade are removed from the Cloudera Data Warehouse UI and CLI

Before this release: Unified Analytics–based Virtual Warehouses for Hive and Impala could be created from both the UI and the CDP CLI. Existing Unified Analytics Hive Virtual Warehouses were displayed with a UNIFIED ANALYTICS tag, and Unified Analytics Impala Virtual Warehouses had an Upgrade Now button in the UI. Rebuilding Unified Analytics virtual warehouse was possible, although not supported due to workload and chart version compatibility issues.

After this release: Unified Analytics Virtual Warehouse creation is removed from the CLI (and was already removed from the UI in the older release). The UNIFIED ANALYTICS tag is removed from all Hive Virtual Warehouses, and the Upgrade Now button is removed from Unified Analytics Impala Virtual Warehouses. Upgrade Now. You can manually migrate Unified Analytics–based Virtual Warehouses to the latest version, which does not include Unified Analytics.

Summary: Allow Cloudera Data Visualization to set environment variables from the UI

Before this release: Cloudera Data Visualization supported certain customizations through environment variables, but there was no straightforward way for users to configure these variables from the product UI. Environment variables for the Cloudera Data Visualization application had to be managed outside the UI, and predefined environment variables were not clearly protected from modification.

After this release: You can now add a new environment variable key–value pairs for a Cloudera Data Visualization application directly from the Create and Edit screens. The Cloudera Data Visualization configuration uses the updated UI V2 layout so that its behavior is consistent with other entities such as Virtual Warehouses. Predefined environment variables are blocked from being modified, while newly added variables are applied by restarting the Cloudera Data Visualization instance with the updated configuration.

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

There are no behavioral changes in this release.

Behavior changes in Hive on Cloudera Data Warehouse on cloud

Summary: Performance-related issues for HMS

Before this release: Several performance-related issues for HMS occurred, including stale entries or inconsistent metadata in the database and exceptions during the update operation for multiple table column statistics or for multiple partition-level column statistics.

After this release: To resolve these issues, a backend database exclusive row lock is now introduced. The statistics importer tasks are coordinated so that only one importer task that obtains the lock runs at a time. The other tasks to import or update the statistics for the same table or partition continue to be in the pending queue until the current importer task completes and then releases the lock. By default, a blocked or pending importer task retries the lock 100 times in the 3 secs ~ 33 secs duration until a failure occurs.

You can now configure the number of retries and the interval between retries using the following parameters that you can set on the Cloudera Manager > Clusters > Hive service > Configuration tab:

• The hive.metastore.s4u.nowait.max.retries parameter allows you to set the number of retries to acquire the row lock immediately without waiting. The default value is 100.
• The hive.metastore.s4u.nowait.retry.sleep.interval parameter allows you to set the interval between the retries to acquire a row lock immediately. The default value is 300ms.

Behavior changes in Iceberg on Cloudera Data Warehouse on cloud

There are no behavioral changes in this release.

Behavior changes in Impala on Cloudera Data Warehouse on cloud

Summary: Support for granting and revoking roles directly to users

Before this release: Previously, you could only grant or revoke roles to or from groups. There was no support for managing roles directly at the individual user level through Impala statements.

After this release: You can now grant and revoke roles directly to and from specific users. This update introduces the following SQL statements to simplify access management:

• GRANT ROLE <role_name> TO USER <user_name>
• REVOKE ROLE <role_name> FROM USER <user_name>
• SHOW ROLE GRANT USER <user_name>

Apache Jira: IMPALA-14085

Summary: Optimizing admissiond memory usage

Before this release: In global admission control mode, complex queries generated large RPC payloads that remained uncompressed. These payloads consumed significant memory within the admissiond service while queries were queued, potentially leading to memory pressure.

After this release: Impala now supports compressing query execution request payloads to reduce the memory footprint in the admissiond service. Compressed requests are stored in memory and decompressed only when an admission decision is made. You can control this by using the admission_control_rpc_compress_threshold_bytes startup flag; a positive value enables compression for requests exceeding that threshold, while 0 disables it. For more information, see Impala components

Summary:

New catalogd flag for HMS event sync defaults

Before this release: Previously, disabling event processing globally required you to manually set the impala.disableHmsSync property for every individual database and table.

After this release: The new disable_hms_sync_by_default flag now defines the global default for event processing. If set to true, Impala skips event processing for all tables and databases unless the impala.disableHmsSync property is explicitly set to false at the table or database level. The priority for checking the sync status is the table property, followed by the database property, and finally the global default flag.

Apache Jira: IMPALA-14085