-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Resolve ListingScan projection against table schema including partition columns
#17911
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+52
−13
Merged
Changes from 3 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
c7c120e
resolve projection against `ListingTable` table_schema incl. partitio…
mach-kernel ff5b32f
Merge branch 'main' into mach/listing-scan-serde-proj
mach-kernel d5b46cc
Merge branch 'main' into mach/listing-scan-serde-proj
mach-kernel ce15b83
add new test alongside old one
mach-kernel 7d93b19
Merge branch 'main' into mach/listing-scan-serde-proj
mach-kernel a7f6f1d
name / clarity
mach-kernel e20af06
Merge branch 'main' into mach/listing-scan-serde-proj
mach-kernel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please leave the existing test case so it is clear there is no loss of coverage, and add the new plan as a new test case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original test passes for me (where it should fail, after
cargo clean) onmainrefs:daeb6597a0c7344735460bb2dce13879fd89d7bd182d5dc5e456322664da921f446018a0549e60bcAt any rate, the old plan was 'supposed' to be the new plan! I am happy to make the change if I got this wrong, just wanted to double check 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I think it best is if the changes to the tests illustrate the changes in the code on the behavior of the code
If you change the test and the code in the same PR it is harder to evaluate the impact of your change on behavior.
For example, if the original query now fails, perhaps you can change it to
To show that a test that (incorrectly) used to work no longer does
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a new test alongside the existing one. The difference between the tests is that the new one will have its projection pushed down to the
TableScannode whereas the original doesn't, which covers the projection case for this bug.I could not figure out what kind of assertion change to make to the existing test (it will continue to pass with/without these changes).