-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-8226][SQL]Add function shiftrightunsigned #7035
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. |
|
Merged build started. |
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.
you can construct an seq and use contains()
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.
almost the same thing for the performance point the view? any way it might be more concise by using seq.
|
Test build #35840 has started for PR 7035 at commit |
|
Test build #35840 has finished for PR 7035 at commit
|
|
Merged build finished. Test FAILed. |
|
retest this please |
|
Merged build triggered. |
|
Merged build started. |
|
Test build #35949 has started for PR 7035 at commit |
|
Test build #35949 has finished for PR 7035 at commit
|
|
Merged build finished. Test PASSed. |
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.
space before {
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.
Not just child?
6bdd7f1 to
b973ac7
Compare
|
Merged build triggered. |
|
Merged build started. |
|
Test build #36338 has started for PR 7035 at commit |
|
Test build #36338 has finished for PR 7035 at commit
|
|
Merged build finished. Test FAILed. |
|
Merged build triggered. |
|
Merged build started. |
|
Test build #36346 has started for PR 7035 at commit |
|
Test build #36346 has finished for PR 7035 at commit
|
|
Merged build finished. Test PASSed. |
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.
BinaryExpression?
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.
Or
abstract class BitwiseShiftExpression extends Expression {
def value: Expression
def bits: Expression
...
}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.
Remove it also?
945a45d to
d85ae0b
Compare
|
Merged build triggered. |
|
Merged build started. |
|
Test build #36473 has started for PR 7035 at commit |
|
Test build #36473 has finished for PR 7035 at commit
|
|
Merged build finished. Test FAILed. |
|
Merged build triggered. |
|
Merged build started. |
|
Test build #36476 has started for PR 7035 at commit |
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.
That one is interesting. Have you seen my comment? Can you have a look on that gist: https://gist.github.com/tarekauel/6994983b83a51668c5dc. Am I getting something wrong?
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.
humm, using pattern match with a typed pattern is indeed a best practice in scala rather than type tests and casts. @chenghao-intel any comments?
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.
Just after a second thought the two styles should not have such huge difference. By reducing one parameter: dataType , the testing result is quite close.
https://gist.github.com/zhichao-li/bff04ed95ef72d09d0e9 A: 10 B: 26
but anyway, seems like pattern match with a typed pattern is a little bit faster, if no objections, I'm going to revert to that style.
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.
Yeah, I was surprised too. Thanks for figuring out!
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.
Have you ever try something like https://github.com/apache/spark/pull/7034/files#diff-d788f93e29b4d25cdd7d60328587678bR359 ?
Since the data type is fixed once the expression created, I don't think we need to check the data type during the runtime, even we don't need the pattern match at all in eval (in runtime).
|
Test build #36476 has finished for PR 7035 at commit
|
|
Merged build finished. Test PASSed. |
|
Merged build triggered. |
|
Merged build started. |
|
Test build #36490 has started for PR 7035 at commit |
|
Test build #36490 has finished for PR 7035 at commit
|
|
Merged build finished. Test PASSed. |
|
LGTM, merging this into master, thanks! |
No description provided.