New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-36021][SQL][FOLLOWUP] DT/YM func use field byte to keep consistence #33252
Conversation
@MaxGekk @cloud-fan Should we keep IntervalUnit now after we have DT/YM field byte now? after this pr's code, it's only usage is as string value
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
Test build #140771 has finished for PR 33252 at commit
|
retest this please |
Kubernetes integration test unable to build dist. exiting with code: 1 |
Test build #140773 has finished for PR 33252 at commit
|
Test build #140776 has finished for PR 33252 at commit
|
retest this please |
Kubernetes integration test starting |
Kubernetes integration test starting |
Kubernetes integration test status success |
Kubernetes integration test status success |
@AngersZhuuuu If it is possible, let's delete it (in another PR). |
…tence ### What changes were proposed in this pull request? With more thought, all DT/YM function use field byte to keep consistence is better ### Why are the changes needed? Keep code consistence ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Not need Closes #33252 from AngersZhuuuu/SPARK-36021-FOLLOWUP. Authored-by: Angerszhuuuu <angers.zhu@gmail.com> Signed-off-by: Max Gekk <max.gekk@gmail.com> (cherry picked from commit 89aa16b) Signed-off-by: Max Gekk <max.gekk@gmail.com>
Test build #140778 has finished for PR 33252 at commit
|
What changes were proposed in this pull request?
With more thought, all DT/YM function use field byte to keep consistence is better
Why are the changes needed?
Keep code consistence
Does this PR introduce any user-facing change?
No
How was this patch tested?
Not need