Description
Currently, amoro periodically performs optimization operations on tables and stores their execution information in the table_process table. However, it also periodically executes cleanup operations such as DanglingDeleteFilesCleaningExecutor, OrphanFilesCleaningExecutor, SnapshotsExpiringExecutor, and DataExpiringExecutor. The execution information for these operations is not stored in the table_process
Use case/motivation
No response
Describe the solution
No response
Subtasks
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct