[SPARK-52586][SQL] Introduce AnyTimeType #51293
Closed
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 the abstract class
AnyTimeType
and its companion object that represents the TIME type of any valid precision. Also added the default precision value which is set to 6 (microseconds) at the moment.Why are the changes needed?
inputTypes()
ofExpectsInputTypes
. Apparently, instead of pointing out all valid TIME types: TIME(0), TIME(1), ..., TIME(6), and in the future TIME(7)..TIME(9), devs could refer to onlyAnyTimeType
.DATATYPE_MISMATCH.UNEXPECTED_INPUT_TYPE
which mentions all precisions of the TIME type.Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running the affected and modified test suites:
Was this patch authored or co-authored using generative AI tooling?
No.