Skip to content

branch-4.0: [fix](cloud) Fix SchemaVariablesScanner crash due to incomplete FE response #65994#66014

Open
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-65994-branch-4.0
Open

branch-4.0: [fix](cloud) Fix SchemaVariablesScanner crash due to incomplete FE response #65994#66014
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-65994-branch-4.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #65994

…sponse (#65994)

Problem Summary: When the Thrift connection to FE is unstable, a
partially deserialized TShowVariableResult can contain variable rows
with fewer than four fields. SchemaVariablesScanner accessed fields 0
through 3 unconditionally and could crash the BE process. Validate every
row before accessing its fields and return an InternalError asking the
user to retry when the response is incomplete.

### Release note

Fix a BE crash when scanning variables after receiving an incomplete FE
response; the query now returns an error asking the user to retry.
@github-actions
github-actions Bot requested a review from morningman as a code owner July 24, 2026 10:48
@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?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/9) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.58% (19593/36568)
Line Coverage 36.63% (183367/500568)
Region Coverage 33.17% (142471/429516)
Branch Coverage 34.05% (61638/181030)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 44.44% (4/9) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 71.48% (25573/35775)
Line Coverage 54.40% (271398/498914)
Region Coverage 51.94% (224890/432944)
Branch Coverage 53.36% (96826/181452)

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