tustvold opened a new issue, #5523: URL: https://github.com/apache/arrow-rs/issues/5523
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> Currently `RowSelection` stores a list of `RowSelector`. This is optimised for the case of large runs of skipped or selected rows, allowing this to be pushed down to the underlying decoding machinery. Whilst this works very well for the use-case of skipping data based on the page index, where the selections are necessarily in the thousands of rows, it will potentially degrade in the presence of more granular predicate evaluation, e.g. as performed by `ArrowPredicate`. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> In a similar vein to https://github.com/apache/arrow-rs/pull/1248, we should have different strategies based on the selectivity of the predicate. In particular I would like RowSelection to switch between a `RowSelector` approach that is pushed down to the underlying readers, and a late evaluation approach where it stores a `BooleanBuffer` that is applied to the columns after the fact **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> **Additional context** <!-- Add any other context or screenshots about the feature request here. --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
