j1wonpark opened a new issue, #4297: URL: https://github.com/apache/amoro/issues/4297
### What happened? `optimizing_task_quota.fail_reason` is always persisted as `NULL` for failed optimizing task attempts, even though `TaskRuntime` contains the failure reason. This prevents users from identifying the cause of each retry attempt. ### Affects Versions master (since v0.5.0) ### How to reproduce 1. Complete an optimizing task with a non-null error message. 2. Let AMS persist the task quota. 3. Check `optimizing_task_quota.fail_reason`. The value is `NULL` instead of the task's failure reason. ### Anything else `TaskRuntime.TaskQuota` has a `failReason` field, and the mapper persists it. However, its constructor does not copy `task.getFailReason()`. https://github.com/apache/amoro/blob/ea4ea4cd31ecab35a3d8b7ebf39571d266cac472/amoro-ams/src/main/java/org/apache/amoro/server/optimizing/TaskRuntime.java#L392-L435 ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's Code of Conduct -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
