feat: Integrate CastColumnExpr into PhysicalExprAdapter #20269
+269
−10
Conversation
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
github-actions
bot
added
physical-expr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Rationale for this change
Ensure physical expression schema adaptation uses struct-aware casting so schema evolution for nested structs preserves field ordering, fills missing fields with NULLs, and propagates logical field metadata/nullability correctly.
What changes are included in this PR?
Wire schema adaptation to emit struct-aware cast expressions for column/field mismatches (including metadata and nullability), extend expression property propagation so optimizer logic continues to work, and add unit + integration coverage for struct projection and filtering under schema evolution.
Are these changes tested?
Yes, added new unit tests aswell
Are there any user-facing changes?
No