[fix](result sink) fix error 'Message size exceeds 2GB' with big result row#42304
[fix](result sink) fix error 'Message size exceeds 2GB' with big result row#42304jacktengg wants to merge 1 commit intoapache:masterfrom
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
d62ddb9 to
acd7f28
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
|
We're closing this PR because it hasn't been updated in a while. |
Proposed changes
Issue Number: close #xxx
With big memory result row, it's easy to reach proto buffer message size limit and result in query error of
Message size exceeds 2GB, and currently the row count of result block is fixed to4096 * 8.This PR add a session variable
result_batch_rowsto make it configurable.