Fixed issues in Cloudera Data Warehouse Private Cloud (1.5.3-CHF1)

This section lists issues fixed in this release of the Cloudera Data Warehouse (CDW) service.

DWX-17404: Hive Virtual Warehouse fails to start up when CDW is unable to parse the LDAP bind password: Earlier, the Hive virtual warehouse failed to start up if you specified the following special characters in the LDAP bind credential password: < > & ' " This happened because the HiveServer2 (HS2) pod remained in the CrashLoopBackOff state with the following error in its logs: error parsing conf file:/etc/hive/conf/hive-site.xml com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '&' (code 38) in content after '<' (malformed start element?). at [row,col,system-id]: [388,13,"file:/etc/hive/conf/hive-site.xml"]. This issue has been fixed.
note
If you are on an older release, then the fix becomes available only when you activate the environment in CDW after upgrading to the Private Cloud Data Services 1.5.3-CHF1 release.
CDPD-67593: Count function in Impala gives incorrect results for Iceberg V2 tables: According to TSB 2024-752, Spark compaction may leave dangling delete files, causing incorrect count results on Iceberg V2 tables. This issue has been temporarily fixed by turning off the count(*) optimizations for Iceberg V2 tables. A permanent fix will be available in a future release.
CDPD-66786: Impala returns incorrect results when the optimized Iceberg V2 operator is used: If you are using Impala to read Iceberg V2 tables, then you may have faced an issue of Impala returning incorrect results when the optimized V2 operator is used. This issue has been resolved by disabling the operator by setting DISABLE_OPTIMIZED_ICEBERG_V2_READ = 1 as the default value.

HIVE-28102, IMPALA-12860: Data corruption issues in Iceberg tables due to concurrent compaction and modify statements: Earlier, Hive or Impala DELETE, UPDATE, or MERGE operations on Iceberg V2 tables corrupted the tables if there was a concurrent table compaction from Spark. This happened because when the compaction and modify statements ran in parallel, and the compaction job was committed before the modify statement. In that case, the modify statement’s position to delete files still points to the old files. This issue has been fixed.