Skip to content

[AMORO-3287][amoro-web]format cost time keeping a maximum of 2 time units#3376

Merged
zhoujinsong merged 5 commits into
apache:masterfrom
ihadoop:format_cost_time
Dec 23, 2024
Merged

[AMORO-3287][amoro-web]format cost time keeping a maximum of 2 time units#3376
zhoujinsong merged 5 commits into
apache:masterfrom
ihadoop:format_cost_time

Conversation

@ihadoop
Copy link
Copy Markdown
Contributor

@ihadoop ihadoop commented Dec 21, 2024

Why are the changes needed?

Close #3287 .

Brief change log

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

  • Does this pull request introduce a new feature? (yes / no) no
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@ihadoop ihadoop changed the title Format cost time [AMORO-3287][amoro-web]format cost time keeping a maximum of 2 time units Dec 21, 2024
@ihadoop
Copy link
Copy Markdown
Contributor Author

ihadoop commented Dec 21, 2024

image

Copy link
Copy Markdown
Contributor

@zhoujinsong zhoujinsong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Thanks for the contribution! @ihadoop

@zhoujinsong zhoujinsong merged commit 2d212be into apache:master Dec 23, 2024
zhoujinsong pushed a commit to zhoujinsong/amoro that referenced this pull request Jan 21, 2025
…units (apache#3376)

* add be codes

* add be codes

* add be codes

* revert
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

module:ams-dashboard Ams dashboard module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: The millisecond-level cost time cannot be displayed normally on the page

2 participants