-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[Improvement](storage) reuse schema and rowblockv2 on single scanner_thread #11392
Conversation
a4242b2
to
a96484d
Compare
a96484d
to
bdf3814
Compare
please review again?@dataroaring. I have fixed. thanks |
bdf3814
to
940a9a7
Compare
@morningman-cmy hello, if have time, review it? |
0aca221
to
d55481e
Compare
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
ff7ba2a
to
5b9825f
Compare
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. |
…thread (apache#11392) * support reuse rowblockv2 on single thread
…thread (apache#11392) * support reuse rowblockv2 on single thread
…12322) #11392 made _input_block in each BetaRowsetReaders sharable. However, for some types (e.g. nested array with more than 1 depth), the _column_vector_batches in RowBlockV2 can be nested which means that there is a ColumnVectorBatch inside another ColumnVectorBatch. In this case, the data of inner ColumnVectorBatch may be corrupted because the data of _input_block is copied shallowly to the _output_block.
…thread (apache#11392) (apache#12178) * support reuse rowblockv2 on single thread
Proposed changes
Issue Number: close #11391
Problem summary
after change,rowblockv2 is not key
Checklist(Required)
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...