Remove FilterPushDown dependency on physical plan#2615
Merged
alamb merged 1 commit intoapache:masterfrom May 25, 2022
Merged
Conversation
alamb
approved these changes
May 25, 2022
Contributor
|
Looks like a nice change to me 👍 |
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 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 #2600
Rationale for this change
I would like to move the logical optimization rules to their own crate (#2599) and this
means that they should not depend on the physical plan.
filter_push_down tests currently rely on TableProvider and ExecutionPlan
What changes are included in this PR?
TableSourceinstead ofTableProviderin testsAre there any user-facing changes?
No
Does this PR break compatibility with Ballista?
No