Fix unnecessarily strict check in parquet chunked reader for choosing split locations. #16099
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.
This is a fix that somehow didn't make it into the initial wave of bug fixes for the parquet chunked reader earlier this year.
The code that determines where to do splits needs to be sure it always chooses a location such that the pages that are selected always enclose at least one full row for a list column. This means that you need to see at least 1 full row (2 row boundaries) in the group of pages. The weaklogic was only checking if you had 1 full row within the very last page in the selection, which is unnecessarily strict. We actually ran into some data out in the wild where this was hit.
This PR changes the logic to include all pages within the chunk when doing the check instead of just the last one.
Checklist