Uh oh!
There was an error while loading. Please reload this page.
avoid iterator materialization in column index lookup - #703
Merged
Conversation
alamb
approved these changes
Jul 12, 2021
unkloud pushed a commit
to unkloud/datafusion
that referenced
this pull request
Mar 23, 2025
* latest df * revert changes to test
HairstonE pushed a commit
to HairstonE/datafusion
that referenced
this pull request
Oct 7, 2025
* fix pushdown for pyarrow filter IsNull The conversion was incorrectly passing in the expression itself as the `nan_as_null` argument. This caused the pushdown to silently fail. * expand the Expr::Literal's that can be used in PyArrowFilterExpression Closesapache#703
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Rationale for this change
Follow up for #605.
What changes are included in this PR?
Avoid unnecessary iterator materialization based on the suggestion from #605 (comment).
Are there any user-facing changes?
no