Skip to content

branch-4.0: [fix](fe) Show warm-up timestamps with date#64875

Open
bobhan1 wants to merge 1 commit into
apache:branch-4.0from
bobhan1:branch-4.0-pick-64606
Open

branch-4.0: [fix](fe) Show warm-up timestamps with date#64875
bobhan1 wants to merge 1 commit into
apache:branch-4.0from
bobhan1:branch-4.0-pick-64606

Conversation

@bobhan1

@bobhan1 bobhan1 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Backport #64606 to branch-4.0.

Original PR: #64606
Original commit: 98d22f8

SHOW WARM UP JOB detailed SyncStats should display last_trigger_ts, last_finish_ts, and progress_trigger_ts with full date and time instead of HH:mm:ss only.

Release note

SHOW WARM UP JOB detailed SyncStats now displays warm-up timestamp fields with full date and time.

Check List

  • Test: Unit Test
    • ./run-fe-ut.sh --run org.apache.doris.cloud.WarmUpStatsTest,org.apache.doris.cloud.CloudWarmUpJobTableFilterTest

### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: Event-driven warm-up detailed SyncStats serialized last_trigger_ts, last_finish_ts, and progress_trigger_ts with only HH:mm:ss. When a job spans dates, the output cannot identify which day the event happened. BE reports these values as epoch milliseconds, so FE can render them directly as yyyy-MM-dd HH:mm:ss while preserving empty strings for unset timestamps.

### Release note

SHOW WARM UP JOB detailed SyncStats now displays warm-up timestamp fields with full date and time.

### Check List (For Author)

- Test: Unit Test
    - ./run-fe-ut.sh --run org.apache.doris.cloud.WarmUpStatsTest,org.apache.doris.cloud.CloudWarmUpJobTableFilterTest
- Behavior changed: Yes. Detailed warm-up timestamp strings now include the date.
- Does this need documentation: No

(cherry picked from commit 98d22f8)
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@bobhan1 bobhan1 changed the title [branch-4.0][fix](fe) Show warm-up timestamps with date branch-4.0: [fix](fe) Show warm-up timestamps with date Jun 26, 2026
@bobhan1 bobhan1 marked this pull request as ready for review June 26, 2026 03:49
@bobhan1 bobhan1 requested a review from morningman as a code owner June 26, 2026 03:49
@bobhan1

bobhan1 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉
Increment coverage report
Complete coverage report

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants