Filter pushdown #2310
Closed
Filter pushdown #2310
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
Contributor
Author
Closed
Contributor
|
Thank you for this, I intend to explore the design space for this a bit this afternoon and report back. My main concern is being able to handle this in the sync part of the codebase, as this will both likely be simpler, but also benefit both APIs. |
Contributor
Made reasonable progress on this, I intend to polish this up and push up a draft tomorrow |
Contributor
|
I think this can be closed now? |
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.
Which issue does this PR close?
Closes #.
Rationale for this change
Add filter pushdown for parquet async reader. This should enable push down of row-level filter predicates to the parquet decoder allowing us to avoid decoding overhead as well as (with some other tweaks) IO overhead when we have page index.
This will need quite a bit more spit and polish but wanted to get feedback on the basic API
What changes are included in this PR?
Are there any user-facing changes?