cxxiii opened a new issue, #3724: URL: https://github.com/apache/amoro/issues/3724
### 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? In the optimizing management Web UI, displaying the Occupation results for each table should call the calculateQuotaOccupy function, as shown below: <img width="778" height="666" alt="Image" src="https://github.com/user-attachments/assets/6d47a638-4eea-491f-9a68-82b3ac679a05"; /> When scheduling a table for optimization, we should also calculate its Occupation to determine its scheduling priority, as shown below: <img width="809" height="475" alt="Image" src="https://github.com/user-attachments/assets/60f13635-019b-45ee-98c6-e457bee9358b"; /> Since these two calculations are nearly identical, we can merge them to maintain consistency and improve code maintainability. ### How should we improve? Implement the only calculateQuotaOccupy function in OptimizingUtil. ### 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]
