Skip to content

[refactor](fragment mgr) move report logic to pipeline fragment context to remove callback parameter from ctor (#62500)#62549

Merged
yiguolei merged 1 commit intoapache:branch-4.1from
yiguolei:branch-4.1
Apr 16, 2026
Merged

[refactor](fragment mgr) move report logic to pipeline fragment context to remove callback parameter from ctor (#62500)#62549
yiguolei merged 1 commit intoapache:branch-4.1from
yiguolei:branch-4.1

Conversation

@yiguolei
Copy link
Copy Markdown
Contributor

What problem does this PR solve?

cherry-pick #62500

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Apr 16, 2026

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?

@yiguolei
Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/236) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.03% (19895/37513)
Line Coverage 36.58% (187456/512416)
Region Coverage 32.90% (145565/442476)
Branch Coverage 34.04% (63779/187378)

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 64.41% (152/236) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 71.54% (26271/36720)
Line Coverage 54.46% (278152/510699)
Region Coverage 51.87% (231556/446420)
Branch Coverage 53.19% (99942/187904)

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Apr 16, 2026
@github-actions
Copy link
Copy Markdown
Contributor

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Copy Markdown
Contributor

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit 8de7a90 into apache:branch-4.1 Apr 16, 2026
27 of 31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants