[Feature] Add input stream of stripe streams in stripe reader. #270
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
16 tasks
morningman
pushed a commit
to apache/doris
that referenced
this pull request
Mar 3, 2025
…#45966) ### What problem does this PR solve? related: apache/doris-thirdparty#270 Problem Summary: The original merge io mechanism `MergeRangeFileReader` requires that the range must be read in order, and the ranges can be out of order, so the range cannot be read back. And if you turn on delayed materialization of orc complex types, you will need to present a stream readback scenario, such as `select struct_element(info, 'age'), id from test_orc_struct, where struct_element(info, 'name') = 'Alice'`. When late materialization is turned on, the present stream of the parent node `info` will be read first after `name` is read. When reading `age`, the parent node `info` needs to be read back. So the late materialization of the orc complex type cannot be turned on at present.
koarz
pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
…apache#45966) ### What problem does this PR solve? related: apache/doris-thirdparty#270 Problem Summary: The original merge io mechanism `MergeRangeFileReader` requires that the range must be read in order, and the ranges can be out of order, so the range cannot be read back. And if you turn on delayed materialization of orc complex types, you will need to present a stream readback scenario, such as `select struct_element(info, 'age'), id from test_orc_struct, where struct_element(info, 'name') = 'Alice'`. When late materialization is turned on, the present stream of the parent node `info` will be read first after `name` is read. When reading `age`, the parent node `info` needs to be read back. So the late materialization of the orc complex type cannot be turned on at present.
kaka11chen
added a commit
to kaka11chen/doris
that referenced
this pull request
Jun 20, 2025
…apache#45966) related: apache/doris-thirdparty#270 Problem Summary: The original merge io mechanism `MergeRangeFileReader` requires that the range must be read in order, and the ranges can be out of order, so the range cannot be read back. And if you turn on delayed materialization of orc complex types, you will need to present a stream readback scenario, such as `select struct_element(info, 'age'), id from test_orc_struct, where struct_element(info, 'name') = 'Alice'`. When late materialization is turned on, the present stream of the parent node `info` will be read first after `name` is read. When reading `age`, the parent node `info` needs to be read back. So the late materialization of the orc complex type cannot be turned on at present.
kaka11chen
added a commit
to kaka11chen/doris
that referenced
this pull request
Jun 20, 2025
…apache#45966) related: apache/doris-thirdparty#270 Problem Summary: The original merge io mechanism `MergeRangeFileReader` requires that the range must be read in order, and the ranges can be out of order, so the range cannot be read back. And if you turn on delayed materialization of orc complex types, you will need to present a stream readback scenario, such as `select struct_element(info, 'age'), id from test_orc_struct, where struct_element(info, 'name') = 'Alice'`. When late materialization is turned on, the present stream of the parent node `info` will be read first after `name` is read. When reading `age`, the parent node `info` needs to be read back. So the late materialization of the orc complex type cannot be turned on at present.
kaka11chen
added a commit
to kaka11chen/doris
that referenced
this pull request
Jun 20, 2025
…apache#45966) related: apache/doris-thirdparty#270 Problem Summary: The original merge io mechanism `MergeRangeFileReader` requires that the range must be read in order, and the ranges can be out of order, so the range cannot be read back. And if you turn on delayed materialization of orc complex types, you will need to present a stream readback scenario, such as `select struct_element(info, 'age'), id from test_orc_struct, where struct_element(info, 'name') = 'Alice'`. When late materialization is turned on, the present stream of the parent node `info` will be read first after `name` is read. When reading `age`, the parent node `info` needs to be read back. So the late materialization of the orc complex type cannot be turned on at present.
kaka11chen
added a commit
to kaka11chen/doris
that referenced
this pull request
Jun 24, 2025
…apache#45966) related: apache/doris-thirdparty#270 Problem Summary: The original merge io mechanism `MergeRangeFileReader` requires that the range must be read in order, and the ranges can be out of order, so the range cannot be read back. And if you turn on delayed materialization of orc complex types, you will need to present a stream readback scenario, such as `select struct_element(info, 'age'), id from test_orc_struct, where struct_element(info, 'name') = 'Alice'`. When late materialization is turned on, the present stream of the parent node `info` will be read first after `name` is read. When reading `age`, the parent node `info` needs to be read back. So the late materialization of the orc complex type cannot be turned on at present.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.