[SPARK-50644][FOLLOWUP][SQL] Fix scalar cast in the shredded reader. #49293
Conversation
This file contains 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
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?
We mostly use the
Castexpression to implement the cast, but we need some custom logic for certain type combinations. We already have special handling forlong/decimal -> timestampinVariantGet.cast, so we should do the same thing inScalarCastHelperto ensure consistency.ScalarCastHelperalso needs special handling fordecimal -> stringto strip any trailing zeros.Why are the changes needed?
To ensure that cast on shredded variant has the same semantics as cast on unshredded variant.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit tests. They would fail without the change.
Was this patch authored or co-authored using generative AI tooling?
No.