-
Notifications
You must be signed in to change notification settings - Fork 2k
Unify cast handling by removing CastColumnExpr branches in pruning and ordering equivalence
#21545
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
+80
−130
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c4b4893
Refactor cast handling in pruning and equivalence
kosiew 2997638
Refactor CastExpr with new_with_target_field
kosiew d5f3e1a
Rename, refactor, and simplify casting logic
kosiew 0bc0453
Refactor casting handling in pruning logic
kosiew de93866
Add nested-field limitation comment in CastExpr
kosiew 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
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
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
Oops, something went wrong.
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.
Since this comment was removed I'm curious what the current state of this is.
AFAIK:
"get_field("col", 'field')_min"?).If this comment is still true lets preserve it.
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.
Good point. This PR does not add nested-field pruning support, and I agree the old comment was still documenting a real limitation rather than a CastColumnExpr-only detail. The branch was collapsed as part of the CastExpr unification, but the nested-field/statistics naming question is still unchanged.
I will restore the note in the unified CastExpr handling path, adjusted to avoid referencing CastColumnExpr, and keep it clear that this PR only preserves existing behavior. I do not plan to add nested-field pruning tests here because this PR intentionally does not change that behavior; those should come with the future nested-field pruning/statistics work.