Cloudera Docs

Behavior changes in Cloudera Data Warehouse on premises 1.5.5 SP3

Behavioral changes for Cloudera Data Warehouse on premises 1.5.5 Service Pack 3 introduce functional adjustments to Cloudera Data Warehouse components.

Behavior changes in Cloudera Data Warehouse on premises

Summary: Changes to the action menu labels for Environments, Virtual Warehouses, and Database Catalogs in Cloudera Data Warehouse
Before this release: When clicking the action menu for Environments, Virtual Warehouses, or Database Catalogs, the Edit option was available to directly modify the resource configurations.
After this release: The Edit option is no longer available in the Action menu. It is replaced by the Details option, which opens the resource details page. From this page, you can view the resource metadata and perform configuration updates that were previously accessed through the Edit option.

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

There are no behavior changes in this release.

Behavior changes in Hive on Cloudera Data Warehouse on premises

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 on the Cloudera Manager > Clusters > Hive service > Configuration tab:

  • The hive.metastore.s4u.nowait.max.retries parameter configures the maximum number of attempts to acquire the row lock. The default value is 100.
  • The hive.metastore.s4u.nowait.retry.sleep.interval parameter configures the duration to wait between retry attempts. The default value is 300ms.

Behavior changes in Iceberg on Cloudera Data Warehouse on premises

There are no behavior changes in this release.

Behavior changes in Impala on Cloudera Data Warehouse on premises

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. Managing roles directly at the individual user level through Impala statements was not supported.
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 synchronization defaults
Before this release: Previously, disabling event processing for the majority of databases and tables while leaving it enabled for a limited number required you to manually set the impala.disableHmsSync property on 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 synchronization status is the table property, followed by the database property, and finally the global default flag.

Apache Jira: IMPALA-14131

Behavior changes in Trino on Cloudera Data Warehouse on premises

DWX-22618: Summary: Support added for deleting Trino configuration keys
Before this release: Trino configuration key-value pairs added through the UI could not be deleted from the configuration table.
After this release: The UI now includes a delete button on each row of the Trino configuration table. Users can now remove Trino configuration keys directly through the interface, though system-critical keys and connector configurations remain protected and cannot be deleted.