baiyangtx opened a new issue, #3777:
URL: https://github.com/apache/amoro/issues/3777

   ### 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, the Optimizing page displays the information of all tables' 
Optimizing Processes at the table level. This design implicitly reflects an 
internal AMS implementation logic, each table can have only one active 
Optimizing Process at a time, and OptimizingStatus is not the status of the 
Process itself, but rather a table-level status.
   
   Other maintenance actions in AMS—such as Expire Snapshot, currently have no 
way to be displayed on the frontend, even though they are just as important as 
file-compaction.
   
   This issue aims to refactor the Optimizing-related pages by introducing a 
**Processes** view that breaks the “one-table-one-process” limitation and, in 
the future, display **all maintenance operations** (e.g., Expire Snapshot, 
Clean Orphan Files) as different Processes.
   
   ### How should we improve?
   
   <img width="2984" height="580" alt="Image" 
src="https://github.com/user-attachments/assets/c4ce522e-7de4-43c2-8b8c-f2e921de6f90";
 />
   
   First, the sidebar item “Optimizing” will be renamed to “Execution,” 
indicating that this section displays what AMS is currently running.
   
   Second, the Tables tab will be retained; it will continue to present, at the 
table level, an aggregated view of each table’s currently active Processes and 
resource usage.
   
   <img width="3012" height="562" alt="Image" 
src="https://github.com/user-attachments/assets/45c81ea2-a971-4c92-a73e-89b97a633003";
 />
   
   Finally, a new **Processes** tab will be introduced, listing all **Active 
Processes**—both the existing TableOptimizingProcess and any new Processes that 
represent table maintenance actions.
   
   ### 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]

Reply via email to