Skip to content

branch-4.1: [fix](be) Report stream load size limits in MiB #66224 - #66351

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66224-branch-4.1
Aug 5, 2026
Merged

branch-4.1: [fix](be) Report stream load size limits in MiB #66224#66351
yiguolei merged 1 commit into
branch-4.1from
auto-pick-66224-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #66224

@github-actions
github-actions Bot requested a review from yiguolei as a code owner August 1, 2026 14:14
@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

Stream Load body-size limit errors display raw byte counts next to BE
configuration items whose names and values are expressed in MB, making
the message misleading. Report both the actual body size and configured
limit in MiB for JSON Stream Load, CSV Stream Load, and HTTP Stream. The
limit calculation and rejection behavior are unchanged.
@yiguolei
yiguolei force-pushed the auto-pick-66224-branch-4.1 branch from 27683a3 to 0b8ac31 Compare August 5, 2026 03:39
@yiguolei

yiguolei commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

run buildall

@yiguolei
yiguolei merged commit af495a9 into branch-4.1 Aug 5, 2026
30 of 35 checks passed
@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (21/21) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 73.65% (30347/41204)
Line Coverage 57.55% (332843/578374)
Region Coverage 54.48% (277240/508885)
Branch Coverage 55.38% (123885/223682)

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.

3 participants