[AMORO-2519] Improve the display of Duration in the page of Optimizing>Tables to make it more user-friendly#3694
Merged
xxubai merged 1 commit intoapache:masterfrom Jul 28, 2025
Conversation
…g>Tables to make it more user-friendly
xxubai
approved these changes
Jul 27, 2025
Jzjsnow
added a commit
to Jzjsnow/amoro
that referenced
this pull request
Aug 20, 2025
…g>Tables to make it more user-friendly (apache#3694) (cherry picked from commit f91477e)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are the changes needed?
Currently, the display of Duration in the page of Optimizing>Tables is different from that on Optimizing process detail page. Also the display format is not as readable and friendly as the results displayed in the hover box.
Close #2519.
Brief change log
Before:
After:
How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before making a pull request
Documentation