zhangwl9 opened a new issue, #4212: URL: https://github.com/apache/amoro/issues/4212
### Search before asking - [x] I have searched in the [issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no similar issues. ### What would you like to be improved? Currently, dangling delete files cleaning is implemented as a standalone scheduler task (DanglingDeleteFilesCleaningExecutor) that runs independently from other table processes. This approach has several limitations: Inconsistent architecture: Other table processes (like SnapshotsExpiringProcess) use the ProcessFactory plugin system, but dangling delete files cleaning uses a separate scheduler, making the codebase inconsistent Limited flexibility: The current implementation cannot leverage the unified process management, execution engine selection, or plugin configuration system Duplication of logic: Scheduling, state tracking, and execution logic are duplicated between dangling delete files cleaning and other table processes Hard to extend: Adding new features like custom execution engines or advanced triggering strategies requires modifying the core scheduler ### How should we improve? Refactor dangling delete files cleaning to use the ProcessFactory plugin system. ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Subtasks _No response_ ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/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]
