[SPARK-36049][SQL] Remove IntervalUnit#33265
[SPARK-36049][SQL] Remove IntervalUnit#33265AngersZhuuuu wants to merge 4 commits intoapache:masterfrom
Conversation
|
Kubernetes integration test starting |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Kubernetes integration test status success |
|
Test build #140794 has finished for PR 33265 at commit
|
|
Test build #140795 has finished for PR 33265 at commit
|
|
FYI @MaxGekk |
MaxGekk
left a comment
There was a problem hiding this comment.
LGTM in general except of a comment.
| def intervalUnits: Seq[UTF8String] = { | ||
| Seq(yearStr, | ||
| monthStr, | ||
| weekStr, | ||
| dayStr, | ||
| hourStr, | ||
| minuteStr, | ||
| secondStr, | ||
| millisStr, | ||
| microsStr) |
There was a problem hiding this comment.
Is it used somewhere except of tests? Just wonder why did you move it from ExpressionParserSuite?
There was a problem hiding this comment.
Is it used somewhere except of tests? Just wonder why did you move it from
ExpressionParserSuite?
Move back, how about current?
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
@AngersZhuuuu Could you re-trigger GitHub actions, please. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
+1, LGTM. Merging to master/3.2. |
### What changes were proposed in this pull request? Remove IntervalUnit ### Why are the changes needed? Clean code ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Not need Closes #33265 from AngersZhuuuu/SPARK-36049. Lead-authored-by: Angerszhuuuu <angers.zhu@gmail.com> Co-authored-by: Maxim Gekk <max.gekk@gmail.com> Signed-off-by: Max Gekk <max.gekk@gmail.com> (cherry picked from commit fef7e17) Signed-off-by: Max Gekk <max.gekk@gmail.com>
|
Test build #140810 has finished for PR 33265 at commit
|
|
Test build #140816 has finished for PR 33265 at commit
|
What changes were proposed in this pull request?
Remove IntervalUnit
Why are the changes needed?
Clean code
Does this PR introduce any user-facing change?
No
How was this patch tested?
Not need