zhang-arvin commented on issue #4431: URL: https://github.com/apache/amoro/issues/4431#issuecomment-6077446734
@zhang-arvin here — I'd like to take this. Root-cause hypothesis: since 0.9, `close()` / failed commit on an optimizing process both route through `completeProcess(false)`, so disabling self-optimizing is recorded as a process *failure* and the process never reaches CLOSED — the `table_process` row stays RUNNING and Dashboard Cancel cannot change it. Plan: 1. Distinguish "process closed because optimizing was disabled" from a real failure in the complete/cancel path. 2. Ensure the process transitions to CLOSED and the failure counter is not incremented. 3. Add a regression test asserting the transition on self-optimizing disable. Please assign this to me if convenient. -- 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]
