[SPARK-52779][SQL][CONNECT] Support TimeType literal in Connect #51462
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
|
ping @MaxGekk to take a look, please. |
dengziming
changed the title
|
@peter-toth Could you review this PR since you are working on similar one: #51464 |
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?
Support TimeType literal in Spark Connect.
Why are the changes needed?
Part of SPARK-51162 to introduce TimeType
Does this PR introduce any user-facing change?
Yes, TimeType literals are supported in Connect, we can use functions such as
org.apache.spark.sql.functions.lit()to pass a time literal.How was this patch tested?
Added some unit tests.
Was this patch authored or co-authored using generative AI tooling?
No.