[SPARK-48399][SQL] Teradata: ByteType should map to BYTEINT instead of BYTE(binary) #46715
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
|
cc @dongjoon-hyun @cloud-fan @LuciferYang thanks |
dongjoon-hyun
approved these changes
May 24, 2024
|
Thank you @dongjoon-hyun, We can add a follow-up on the legacy configuration if someone considers it necessary. Merged to master |
|
late LGTM |
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?
According to the doc of Teradata and Teradata jdbc, BYTE represents binary type in Teradata, while BYTEINT is used for tinyint.
Why are the changes needed?
Bugfix
Does this PR introduce any user-facing change?
Yes, ByteType used to be stored as binary type in Teradata, now it has become BYTEINT.
(The use-case seems rare, the migration guide or legacy config are pending reviewer's comments)
How was this patch tested?
new tests
Was this patch authored or co-authored using generative AI tooling?
no