-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](string64) fix coredump caused by ColumnArray<ColumnStr<uint64_t>>::insert_indices_from #43624
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.
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
3241ad5 to
1ebcfc0
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
6fe1301 to
d6b0468
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
a0c5a3a to
9482abe
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
…>>::insert_indices_from
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
HappenLee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…>>::insert_indices_from (#43624)
…>>::insert_indices_from (#43624)
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
In order to avoid the problem of total string length of a
ColumnStr<uint32_t>column exceeds the 4G limit, hash join operator callMutableBlock::merge_ignore_overflowto collect build data.After finishing collecting build data, a
ColumnStr<uint32_t>column will be converted toColumnStr<uint64_t>if the total string length exceeds the 4G limit by callingBlock::replace_if_overflow.When hash join operator ouput join result block, it need to calls
ColumnStr<T>::insert_indices_fromto fill a string column, which is able to handle bothColumnStr<uint32_t>andColumnStr<uint64_t>. Every column which may include string sub-columns should also callinsert_indices_frommethod of it's sub-column to handle bothColumnStr<uint32_t>andColumnStr<uint64_t>, or else column cast will fail.Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)