[SPARK-55868][SQL][Tests] Fix Predicate Pushdown for InMemoryTable for V2Filters#54666
Open
szehon-ho wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-55868][SQL][Tests] Fix Predicate Pushdown for InMemoryTable for V2Filters#54666szehon-ho wants to merge 1 commit intoapache:masterfrom
szehon-ho wants to merge 1 commit intoapache:masterfrom
Conversation
peter-toth
approved these changes
Mar 7, 2026
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.
What changes were proposed in this pull request?
Fix some Predicate (ie V2 Filter) name match in the filter pushdown code (for the test table supporting V2Filter of InMemoryDataSource for DSV2)
Why are the changes needed?
These Predicate names are not matching, and no filters are accepted by this test table. This was found in #54459
Does this PR introduce any user-facing change?
No, tests only
How was this patch tested?
Running affect tests
Was this patch authored or co-authored using generative AI tooling?
Yes, cursor