-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-8759][SQL] add default eval to binary and unary expression according to default behavior of nullable #7157
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
Conversation
|
Merged build triggered. |
|
cc @rxin |
|
Merged build triggered. |
|
Merged build triggered. |
|
Merged build started. |
2 similar comments
|
Merged build started. |
|
Merged build started. |
|
Test build #36255 has started for PR 7157 at commit |
|
Test build #36252 has started for PR 7157 at commit |
|
Test build #36256 has started for PR 7157 at commit |
|
Test build #36255 has finished for PR 7157 at commit
|
|
Merged build finished. Test FAILed. |
|
Test build #36256 has finished for PR 7157 at commit
|
|
Merged build finished. Test PASSed. |
|
Test build #36252 has finished for PR 7157 at commit
|
|
Merged build finished. Test PASSed. |
|
waiting for #7175 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add scala doc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will add it during rebase, thanks for reminding!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just leave it as unimplemented, so developer will notice that during coding, not runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There maybe exceptional cases that user need to override eval, at that time they don't need to implement nullSafeEval.
|
Thank you for working on this @cloud-fan.This PR definitely will save the code, but I have some concerns on the interface updating, not about what you did in this PR, but in general:
|
|
hi @chenghao-intel , thanks for looking into this! I agree with your opinions, but have some other thoughts:
|
|
Build triggered. |
|
Build started. |
|
Test build #36562 has started for PR 7157 at commit |
|
Test build #36562 has finished for PR 7157 at commit
|
|
Build finished. Test PASSed. |
|
Merged build triggered. |
|
Merged build started. |
|
Test build #36571 has started for PR 7157 at commit |
|
Test build #36571 has finished for PR 7157 at commit
|
|
Merged build finished. Test PASSed. |
|
Hi @rxin , can you review it please? It's very easy to get conflict and I have to rebase it again and again... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you update the javadoc above to include param doc for f, defining what the input / output is?
|
Looks good to me. Some comments about naming. |
|
Merged build triggered. |
|
Merged build started. |
|
Test build #36635 has started for PR 7157 at commit |
|
Test build #36635 has finished for PR 7157 at commit
|
|
Merged build finished. Test PASSed. |
|
Thanks. I've merged this. |
We have
nullSafeCodeGento provide default code generation for binary and unary expression, and we can do the same thing foreval.