Improve documentation on implementing Parquet predicate pushdown #7370
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
This was referenced Apr 1, 2025
kylebarron
reviewed
Apr 1, 2025
kylebarron
reviewed
Apr 1, 2025
Co-authored-by: Weston Pace <[email protected]> Co-authored-by: Kyle Barron <[email protected]>
Contributor
Author
|
Thank you all for correcting what seems to be pretty atrocious typos on my part |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
Rationale for this change
It is not clear from the documentation why the parquet crate has no row group / data page predicate evaluation features as described on #7348
What changes are included in this PR?
Are there any user-facing changes?
Docs only, no functional change