zhangwl9 opened a new issue, #4202: URL: https://github.com/apache/amoro/issues/4202
### 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? PR #4116 extracted TableProcessStore from AmoroProcess and PR #4107 migrated SnapshotsExpiring to the new Process architecture. However, four table maintenance Executors still run on the legacy PeriodicTableScheduler infrastructure: 1. OrphanFilesCleaningExecutor — cleans orphan files via TableMaintainer.cleanOrphanFiles() 2. DataExpiringExecutor — expires data via TableMaintainer.expireData() 3. DanglingDeleteFilesCleaningExecutor — cleans dangling delete files via TableMaintainer.cleanDanglingDeleteFiles() 4. TagsAutoCreatingExecutor — auto-creates tags via TableMaintainer.autoCreateTags() These Executors suffer from the same limitations that SnapshotsExpiringExecutor had before migration: - No failure retry : exceptions are caught and logged only, never retried - Dual scheduling logic : legacy InlineTableExecutors + new ActionCoordinatorScheduler coexist, increasing maintenance cost ### How should we improve? Migrate the four Executors to TableProcess implementations under IcebergProcessFactory , following the exact pattern established by SnapshotsExpiringProcess → SnapshotsExpiringExecutor migration. ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Subtasks - Migrate OrphanFilesCleaningExecutor → OrphanFilesCleaningProcess - Migrate DataExpiringExecutor → DataExpiringProcess - Migrate DanglingDeleteFilesCleaningExecutor → DanglingDeleteFilesCleaningProcess - Migrate TagsAutoCreatingExecutor → TagsAutoCreatingProcess (with ICEBERG-only restriction) ### 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]
