[SPARK-52493][SQL] Support TIMESTAMP WITHOUT TIME ZONE #51181
Closed
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
MaxGekk
changed the title
|
@srielau Please, take a look at the PR. Also cc @gengliangwang. |
dongjoon-hyun
approved these changes
Jun 16, 2025
|
cc @yaooqinn |
yaooqinn
approved these changes
Jun 17, 2025
gengliangwang
approved these changes
Jun 17, 2025
|
Merging to master. Thank you, @dongjoon-hyun @yaooqinn @gengliangwang for review. |
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?
In the PR, I propose to introduce a synonym for the existing type
TIMESTAMP_NTZas the SQL standard defines:TIMESTAMP WITHOUT TIME ZONE.Why are the changes needed?
TIMEtype, see [SPARK-51563][SQL] Support the fully qualified type name TIME(n) WITHOUT TIME ZONE #51177Does this PR introduce any user-facing change?
No, it just extends the existing syntax.
How was this patch tested?
By running the modified test suite:
Was this patch authored or co-authored using generative AI tooling?
No.