Skip to content

[enhance](meta-service)add bvar for fdb process status #59329

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
hello-stephen merged 4 commits into from
Jan 4, 2026
Merged

[enhance](meta-service)add bvar for fdb process status #59329

hello-stephen merged 4 commits into from
Jan 4, 2026

Conversation

@koarz
Copy link
Contributor

@koarz koarz commented Dec 24, 2025

What problem does this PR solve?

Issue Number: close #xxx

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
Contributor

Thearas commented Dec 24, 2025

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?

@koarz
Copy link
Contributor Author

koarz commented Dec 24, 2025

run buildall

gavinchou
gavinchou reviewed Dec 24, 2025
View reviewed changes
@hello-stephen
Copy link
Contributor

hello-stephen commented Dec 24, 2025

Cloud UT Coverage Report

Increment line coverage 92.68% (76/82) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 79.54% (1773/2229)
Line Coverage 64.88% (31351/48325)
Region Coverage 65.40% (15581/23825)
Branch Coverage 56.00% (8282/14790)

@koarz
Copy link
Contributor Author

koarz commented Dec 24, 2025

run buildall

gavinchou
gavinchou reviewed Dec 24, 2025
View reviewed changes
@hello-stephen
Copy link
Contributor

hello-stephen commented Dec 24, 2025

Cloud UT Coverage Report

Increment line coverage 92.59% (75/81) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 79.54% (1773/2229)
Line Coverage 64.87% (31348/48322)
Region Coverage 65.41% (15585/23825)
Branch Coverage 56.02% (8285/14790)

@koarz
Copy link
Contributor Author

koarz commented Dec 26, 2025

run buildall

@doris-robot
Copy link

doris-robot commented Dec 26, 2025

Cloud UT Coverage Report

Increment line coverage 92.59% (75/81) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 79.54% (1773/2229)
Line Coverage 64.83% (31340/48341)
Region Coverage 65.39% (15595/23848)
Branch Coverage 55.98% (8288/14806)

@koarz
Copy link
Contributor Author

koarz commented Dec 30, 2025

run buildall

@doris-robot
Copy link

doris-robot commented Dec 30, 2025

Cloud UT Coverage Report

Increment line coverage 92.59% (75/81) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 79.54% (1773/2229)
Line Coverage 64.85% (31367/48367)
Region Coverage 65.38% (15596/23856)
Branch Coverage 56.03% (8298/14810)

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 31, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 31, 2025

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

@github-actions
Copy link
Contributor

github-actions bot commented Dec 31, 2025

PR approved by anyone and no changes requested.

@gavinchou
Copy link
Contributor

gavinchou commented Jan 2, 2026

run cloud_p0

@gavinchou
Copy link
Contributor

gavinchou commented Jan 2, 2026

run vault_p0

@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 4, 2026

run external

@hello-stephen hello-stephen merged commit 1cbe487 into apache:master Jan 4, 2026
32 of 33 checks passed
github-actions bot pushed a commit that referenced this pull request Jan 4, 2026
@koarz
[enhance](meta-service)add bvar for fdb process status (#59329)
c83bd22
@github-actions github-actions bot mentioned this pull request Jan 4, 2026
Open
github-actions bot pushed a commit that referenced this pull request Jan 4, 2026
@koarz
[enhance](meta-service)add bvar for fdb process status (#59329)
7c48508
@github-actions github-actions bot mentioned this pull request Jan 4, 2026
Merged
yiguolei pushed a commit that referenced this pull request Jan 5, 2026
@github-actions @koarz
branch-4.0: [enhance](meta-service)add bvar for fdb process status #5…
d6db798 
…9329 (#59526)

Cherry-picked from #59329

Co-authored-by: koarz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gavinchou gavinchou gavinchou approved these changes

@w41ter w41ter w41ter approved these changes

@dataroaring dataroaring Awaiting requested review from dataroaring dataroaring is a code owner

+1 more reviewer

@wyxxxcat wyxxxcat wyxxxcat approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. dev/3.1.x dev/4.0.3-merged reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@koarz @Thearas @hello-stephen @doris-robot @gavinchou @w41ter @wyxxxcat @yiguolei