October 4, 2024 - Hotfix

This hotfix release of the Cloudera Data Warehouse (CDW) service on CDP Public Cloud introduces a Runtime fix.

DWX-18477: (Addendum) Merge query failures with reserved keywords as column names

If a reserved keyword is used as a column name in a query, you must escape the keyword by enclosing it within backticks (`). However, If you have merge queries involving Iceberg target tables that use reserved keywords as column names, the backticks are not retained when the merge queries are rewritten to a join query, and the query fails with a "SemanticException" error.

This issue is now fixed as part of an additional fix that was provided in HIVE-28282.

Review the known issues in this release of the Cloudera Data Warehouse (CDW) service on Public Cloud.

DWX-19451: Data Visualization restore job can fail with ignorable errors

After a successful Data Visualization restoration job, the Data Visualization restore job could be in a failed state with the log displaying ignorable errors.

pg_restore: error: could not execute query: ERROR:  sequence "jobs_joblog_id_seq" does not exist
Command was: DROP SEQUENCE public.jobs_joblog_id_seq;
pg_restore: error: could not execute query: ERROR:  table "jobs_joblog" does not exist
Command was: DROP TABLE public.jobs_joblog;
pg_restore: error: could not execute query: ERROR:  sequence "jobs_jobcontent_id_seq" does not exist
Command was: DROP SEQUENCE public.jobs_jobcontent_id_seq;
.......
.......

This issue occurs because the restore job issues commands to DROP all the objects that will be restored, and if any of these objects do not exist in the destination database, such ignorable errors are reported.

This has no functional impact on the restored Data Visualization application. It is noticed that all the backed up queries, datasets, connections, and dashboards are restored successfully and Data Visualization is available for new queries.

None.

DWX-19454: Default Database Catalog does not start in an Azure transparent proxy, private link, and private AKS setup

If you are running a transparent proxy with a private link and private AKS setup in your Azure environment, the Data Warehouse server is unable to connect to the private AKS end point, and the default Database Catalog fails to start.

None.