-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Fix](Variant) VariantRootColumnIterator::read_by_rowids with wrong null map size #33734
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
…ull map size insert_range_from should start from `size` with `count` elements for null map
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 38533 ms |
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 184693 ms |
ClickBench: Total hot run time: 30.25 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
xiaokang
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
…ull map size (apache#33734) insert_range_from should start from `size` with `count` elements for null map
…ull map size (#33734) insert_range_from should start from `size` with `count` elements for null map
* [Fix](Variant Type) forbit distribution info contains variant columns (#33707) * [Fix](Variant) VariantRootColumnIterator::read_by_rowids with wrong null map size (#33734) insert_range_from should start from `size` with `count` elements for null map * [Fix](Variant) check column index validation for extracted columns (#33766)
…ull map size (#33734) insert_range_from should start from `size` with `count` elements for null map
…ull map size
insert_range_from should start from
sizewithcountelements for null mapProposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...