Fixed issues

Fixed issues in Cloudera Data Warehouse on cloud

DWX-22464: CDP CLI validation error when updating Virtual Warehouse t-shirt size to waa in Cloudera Data Warehouse

Previously, the CDP CLI incorrectly rejected updates to an Impala Virtual Warehouse that included waa (Workload Aware Autoscaling) as the t-shirt size, even when the Virtual Warehouse was already configured with waa. The CLI validation only allowed xsmall, small, medium, and large as valid values, causing updates to fail unnecessarily with the following error:

Invalid value for parameter tShirtSize, value: waa, valid values: xsmall, small, medium,
          large.

This issue is resolved by ensuring that CDP CLI updates to Virtual Warehouses already configured with waa as the t-shirt size are no longer rejected.

DWX-19998: Private AKS cluster updates blocked by Kubernetes CIDR configuration in the UI

Previously, in Cloudera Data Warehouse on Azure, the Enable IP-CIDR for Kubernetes cluster option was editable for private AKS clusters. When modifications were made to this option, Cloudera Data Warehouse sent a Kubernetes cluster CIDR value to the backend (including invalid values such as 0.0.0.0). For private AKS environments this configuration is not applicable, and sending a value could block cluster updates, including changes to cluster admin groups.

This issue is now resolved by disabling the Enable IP-CIDR for Kubernetes cluster option for private AKS clusters in the UI.

DWX-22178: Virtual warehouse t-shirt size change does not update related configurations

Previously, when changing the t-shirt size of a virtual warehouse from xsmall to small, the related configuration values did not automatically update to match the new t-shirt size. This mismatch could cause queries to be planned with an incorrect number of executors, potentially leading to suboptimal query execution, resource allocation issues, and degraded performance.

This issue is now resolved.

DWX-22179: Minidump shipper failing on Azure

Previously, in Azure-based Cloudera Data Warehouse environments, the minidump shipper failed to ship minidumps because its configuration directory was inaccessible. The process attempted to use /home/hive as the configuration directory inside the container, but this path was not writable, causing a PermissionError during initialization and preventing minidump files from being uploaded to cloud storage.

This issue is now resolved. The minidump shipper now sets the AZURE_CONFIG_DIR environment variable to point to a writable directory, and the az login invocation is updated so that authentication and minidump upload to Azure storage complete successfully.

DWX-21083: Read-only users seeing frequent permission denied errors in the Cloudera Data Warehouse UI

Previously, in Cloudera Data Warehouse on cloud, read-only sessions frequently experienced permission denied errors in the UI during normal operations. This occurred because the UI attempted to call the /resources/templatesaza, which requires administrator privileges, even for read-only sessions. As a result, permission-related error messages repeatedly interrupted normal operations despite no privileged actions being performed.

This issue is now resolved.

DWX-21896: Transient UI error for failed resource pool runtime upgrade

Previously, when creating a resource pool, if the associated Database Cluster or Virtual Warehouse runtime upgrade fails, the resulting error message is displayed only temporarily in the UI. Shortly after the failure, the error message vanishes, leaving the UI with no persistent indication that the runtime upgrade failed. This behavior can be misleading, as it might appear that the operation was successful or is still in progress.

This issue is now resolved.

Fixed issues in Hive on Cloudera Data Warehouse on cloud

CDPD-95083: Concurrency issues when updating partition column statistics

Previously, the process for updating partition column statistics involved fetching, modifying, and then updating the statistics. This method caused concurrency issues when multiple clients attempted to update statistics for the same partition at the same time, potentially leading to inaccurate metadata.

This issue is now resolved.

Apache Jira: HIVE-29316

CDPD-95082: Direct SQL failures during partition operations cause stale database entries

Previously, if a failure occurred during direct SQL processing for operations such as adding or dropping partitions, the changes made to the database were not undone before the system fell back to Java Data Objects (JDO) processing.

This issue is now resolved by setting a savepoint in the transaction before direct SQL processing begins. If a failure occurs, the system now rolls back to that savepoint before initiating the JDO fallback, ensuring database consistency.

Apache Jira: HIVE-26976

CDPD-94765: Improved performance for adding columns to tables with many partitions

Previously, adding a column to a table using the CASCADE command could be slow for tables containing a high number of partitions or columns due to unoptimized metadata processing.

This issue is addressed by optimizing the underlying metadata operations and implementing batching. These changes improve performance and efficiency when you run the ALTER TABLE ADD COLUMN CASCADE command on large tables.

Apache Jira: HIVE-28956

CDPD-94764: Performance degradation when adding columns with the cascade option

Previously, after you enabled directSQL, performance degraded when adding columns to a table by using the CASCADE command.

This issue is resolved by implementing a mechanism to reuse new column descriptors between storage descriptors that share the same original column descriptor ID.

Apache Jira: HIVE-29042

CDPD-93175: Incorrect results for n-way joins containing both anti and outer joins

Previously, when you enabled Cost-Based Optimization (CBO) and n-way joins, Hive returned incorrect results for queries that combined anti joins with outer joins.

This issue is resolved by extending the CommonJoinOperator to support the combination of anti joins and outer joins within n-way joins.

Apache Jira: HIVE-29290

CDPD-93166: Incorrect results when an anti-join replaces an IS NULL filter on a nullable column

Previously, when you enabled the automatic conversion of joins with a IS NULL filter to anti-joins, Hive returned incorrect results for certain queries. Specifically, when the HiveAntiSemiJoinRule replaced an IS NULL filter on a nullable column with an anti-join, it generated an incorrect query plan. This resulted in missing rows in the final output compared to when the optimization was disabled.

This issue is resolved by improving the logic within the HiveAntiSemiJoinRule. The fix ensures that the rule correctly handles nullable columns during the transformation process, resulting in accurate query plans and correct data retrieval regardless of whether anti-join conversion is active.

Apache Jira: HIVE-29176

CDPD-79799: High metadata overhead during migration due to table and partition statistics

Previously, during migration or replication, copying statistics for tables with a large number of partitions and columns took a significant amount of time.

This issue is resolved by implementing changes in the Hive Metastore to support dropping statistics for tables, partitions, and columns.

Apache Jira: HIVE-28655

CDPD-55133: Query failure on views containing grouping sets and grouping functions

Previously, queries run against a view failed with a RuntimeException if the view definition included GROUPING functions and GROUPING SETS.

This issue is resolved and the fix ensures that column names within the GROUPING function are correctly expanded to include their associated table and schema aliases during view creation. This allows the parser to successfully match the function arguments with the GROUP BY clause when you select data from the view.

Apache Jira: HIVE-27280

Fixed issues in Cloudera Data Explorer (Hue) on Cloudera Data Warehouse on cloud

CDPD-88276: Data Explorer SAML logout landing page

Previously, Data Explorer did not include a dedicated landing page for SAML logout sessions. This resulted in a lack of clarity regarding the session status after you logged out. This issue is now resolved. Data Explorer now includes a SAML logout landing page that confirms your session has ended and provides an option to log in again.

CDPD-81753: Added a configurable flag to optionally re-enable data preview on database views in Data Explorer

Previously, data preview for database views was disabled by default due to resource strains caused by complex or long-running views, impacting data validation and analysis.

This issue has now been improved by adding the new allow_sample_data_from_views flag, with the default value set to false. Setting this flag to true enables Data Explorer to fetch sample data for database views and thus restore the data preview functionality in the SQL assist panel. You can enable the flag by performing the following steps:

1. Navigate Virtual warehouse > Data Explorer (Hue) > Configuration.
2. In the hue_safety_valve field, specify the following parameter:

   [metastore]
   allow_sample_data_from_views=true

3. Click Apply Changes.

CDPD-45130: Truncating excessive length queries to prevent database indexing errors

Previously, large or complex SQL statements, such as lengthy INSERT queries, were indexed by the Query Processor. This resulted in increased load times for the Job Browser. You can now configure query truncation by using the hue.query-processor.query.max-length property in the Query Processor configuration under dasConf section. By default, no truncation is performed to ensure backward compatibility.

DWX-12703: Impala coordinator workload distribution in active-active configurations

Previously, the Data Explorer client used only one coordinator when Impala was configured in active-active mode. This occurred because Data Explorer did not include support for cookie-based sticky sessions. As a result, the system failed to distribute the workload across multiple coordinators, which impacted production stability and workload balancing.

This issue is now resolved. Data Explorer now supports cookie-based sticky sessions, which allows for effective workload distribution across all available coordinators in active-active Impala environments.

Fixed issues in Impala on Cloudera Data Warehouse on cloud

CDPD-94500: Impala query failure when reading Parquet collections with late materialization

Previously, when an Impala query selected the last row containing a collection value in a row group, the readahead state was not reset. This caused subsequent query failures.

This issue is now resolved by resetting the readahead flag in the column reader whenever it advances to a new row group.

Apache Jira: IMPALA-14619

ENGESC-32075 / IMPALA-14605: Memory leak in global admissiond for cancelled queued queries

Previously, a memory leak occurred in the global admissiond when queries in the admission queue were cancelled due to backpressure. The system identified the cancellation but did not remove the query from the admission state map.

To resolve this memory leak, this fix introduces an asynchronous cleanup mechanism. Cancelled queued queries are now added to a queue for a background process to safely clear them from the admission state map.

Apache Jira: IMPALA-14605

IMPALA-14403: OpenTelemetry TLS detection failed due to case-sensitivity

Previously, Impala failed to enable TLS for OpenTelemetry (OTel) collectors if the URL used uppercase letters (e.g., HTTPS://). The case-sensitive detection logic prevented the client from configuring TLS correctly and occasionally enabled it for non-HTTPS schemes.

This issue is resolved by making the OTel collector URL detection case-insensitive and ensuring TLS is only enabled for valid https schemes.

Apache Jira: IMPALA-14403

CDPD-91155: CatalogD reports misleading TableNotFoundException for workload management tables

Previously, when you used workload management for the first time, CatalogD generated an org.apache.impala.catalog.TableNotFoundException for the sys.impala_query_log and sys.impala_query_live tables. This occurred because the system attempted to refresh metadata for these tables to check their schema version before they were created.

This issue is now resolved by checking for the existence of the workload management tables before initiating a metadata reset. This change ensures that error messages are no longer generated during a successful initialization process.

Apache Jira: IMPALA-14468

IMPALA-14383: Crash when casting timestamp strings with timezone offsets to DATE

Attempting to cast a timestamp string that included a timezone offset (like "+08:00" in "2025-08-31 06:23:24.9392129 +08:00" ) to the DATE data type would cause a crash.

This issue is addressed by adding a check to ensure that the timestamp string length does not exceed the maximum length of the default date-time format. Longer strings will now use a lazily-created format, which prevents the crash.

Apache Jira: IMPALA-14383

IMPALA-14791: Impala crash when viewing failed query plans

Previously, Impala crashed when you used the Web UI to view the plan of a query that failed before execution started.

This issue is addressed by updating the function to handle missing execution summaries. This fix ensures that the Web UI remains stable even when query summaries are unavailable.

Apache Jira: IMPALA-14791

CDPD-99070: CVE-2025-15467 false positive alerts in Impala images

Previously, the Impala Docker image included the openssl-config package when built on top of Chainguard images. This package contained outdated signatures that triggered false positive alerts in CVE scanners, even though the package itself was effectively empty.

This issue is addressed by removing the openssl-config package from the Impala Docker image build process. This removal eliminates the false positive scanner hits without affecting functionality, as the necessary basic configuration is provided by the openssl package.

CDPD-99070

IMPALA-14447: Parallel metadata loading in local catalog mode

Previously, when a query accessed multiple unloaded tables in local catalog mode, Impala loaded the metadata for those tables one after another. This sequential process caused significant latency and performance regressions compared to the legacy catalog mode.

This issue is addressed by parallelizing the table loading process. The fix allows Impala to load and gather metadata for multiple tables simultaneously. You can control the maximum number of threads used for this process by using the new max_stmt_metadata_loader_threads flag, which defaults to 8 threads per query compilation.

Apache Jira: IMPALA-14447

Fixed issues in Iceberg on Cloudera Data Warehouse on cloud

There are no fixed issues in this release.