zhangwl9 opened a new pull request, #4238:
URL: https://github.com/apache/amoro/pull/4238
<!--
Thanks for sending a pull request!
Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://amoro.apache.org/how-to-contribute/
2. If the PR is related to an issue in
https://github.com/apache/amoro/issues, add '[AMORO-XXXX]' in your PR title,
e.g., '[AMORO-XXXX] Your PR title ...'.
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][AMORO-XXXX] Your PR title ...'.
-->
## Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you add a feature, you can talk about its use case.
2. If you fix a bug, you can clarify why it is a bug.
3. Use Fix/Resolve/Close #{ISSUE_NUMBER} to link this PR to its related
issue
-->
Close #4236.
## Brief change log
<!--
Clearly describe the changes made in modules, classes, methods, etc.
-->
This PR introduces a dedicated Maintenance tab in the table details page to
separate maintenance processes (cleanup operations) from optimizing processes,
improving user experience and operational clarity.
Key changes:
- Backend: Add `processCategory` parameter to `getOptimizingProcessesInfo`
API to filter by OPTIMIZING or MAINTENANCE category
- Backend: Add new REST endpoint `/maintenance-types` to fetch
maintenance-specific process types
- Backend: Update `MixedAndIcebergTableDescriptor` to support category-based
filtering with proper type separation
- Frontend: Create reusable `Maintenance.vue` component that wraps
`Optimizing.vue` with maintenance-specific configuration
- Frontend: Add `processCategory` and `cancelModalTitleKey` props to
`Optimizing.vue` for flexible reuse
- Frontend: Register Maintenance tab in table details page alongside
Optimizing tab
## How was this patch tested?
- [ ] Add some test cases that check the changes thoroughly including
negative and positive cases if possible
- [x] Add screenshots for manual tests if appropriate
<img width="1953" height="952" alt="iShot_2026-05-29_12 47 22"
src="https://github.com/user-attachments/assets/1cd3d570-005d-4fe7-8a6c-358cba0d590a";
/>
- [x] Run test locally before making a pull request
## Documentation
- Does this pull request introduce a new feature? (yes / no)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs /
not documented)
--
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]
