Fixed issues for Cloudera Management Console

CDPD-91628, CDPD-98014: In-progress task metadata is cleaned up periodically

Previously, when the task cleanup executor daemon for Cloudera Lakehouse Optimizer ran, it cleaned up the tasks that were in progress . This issue is now fixed. The daemon cleans up only the completed and failed tasks that are not in progress.

CDPD-88828: Duplicate tasks run on table

Previously, Cloudera Lakehouse Optimizer allowed duplicate tasks to run on a table. This issue is now fixed.

CDPD-94583: Filter expression does not transform as expected and fails during the validation step

Previously, when an Iceberg table was created using a DDL command with a bucket transformation specification, and you created a Cloudera Lakehouse Optimizer policy on the table to perform the compaction or rewrite data files tasks, the tasks failed during the validation step. This issue is now fixed.

CDPD-97815: Associations are lost after Cloudera Lakehouse Optimizer restarts

Previously, the following issues occurred when Cloudera Lakehouse Optimizer restarted:

The associations defined using the Cloudera Lakehouse Optimizer UI were lost because they were not persisted.
The namespace-level associations for the tables were not initialized in the registry.

These issues are now fixed.

CDPD-103101: Task event log files accumulate in HDFS after log ingestion in Cloudera Lakehouse Optimizer

Previously, the task event log files in HDFS required manual monitoring and cleanup after the log files were ingested. This issue is now resolved. The task event log files from HDFS are cleaned up automatically after the log files are successfully ingested into the Iceberg table.

CDPD-103026: Cloudera Lakehouse Optimizer task ingestion action fails due to strict timestamp parsing in Spark3

Previously, the task ingestion action failed during Spark validation step because of the strict timestamp parsing in the Spark 3 service. This issue is now resolved.

CDPD-101842, CDPD-101706: Cloudera Lakehouse Optimizer event policies are triggered even after the policies are deleted

Previously, when you tried to associate the event-based policy with an individual table, the association failed abruptly if the policy was already associated with the entire namespace. After you deleted the policy, the event-based scheduler retained the triggers and continued to schedule the table maintenance, which was incorrect. This issue is now resolved.

CDPD-101534, CDPD-101213: List policy API returns unauthorized status for wildcard namespace in Cloudera Lakehouse Optimizer

Previously, the GET /namespaces/{namespace}/policies API returned the 401 Unauthorized error HTTP status code when you entered the asterisk (*) wildcard for the {namespace} parameter. This issue is now resolved.

CDPD-101284, CDPD-100562: The Edit Association page displays all namespaces as associated to the Cloudera Lakehouse Optimizer policy

Previously, when you edited an association for a Cloudera Lakehouse Optimizer policy, the UI incorrectly displayed all the namespaces as associated with the policy or incorrectly displayed all the namespaces as selected. This issue is now resolved.

CDPD-101183, CDPD-100274, CDPD-101104: API-related performance issues impact Lakehouse Optimizer UI response time

Previously, API-related performance issues impacted the View policy page load and the Create Policy process response time in the Lakehouse Optimizer UI. This issue is now resolved.

CDPD-84718: Cloudera Lakehouse Optimizer uses latest Guava library dependencies

Cloudera Lakehouse Optimizer uses the latest com.google.guava:guava 28.1-jre library dependency.