-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[function](hash) add support of murmur_hash3_64 #12923
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
f53339b to
e305681
Compare
winnerhero
left a comment
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.
LGTM
b58e971 to
ecac181
Compare
Also delete duplicated code for murmur_hash3_32
ecac181 to
8ce55c0
Compare
| } | ||
|
|
||
| // modify from https://github.com/aappleby/smhasher/blob/master/src/MurmurHash3.cpp | ||
| static uint32_t murmur_hash3_32(const void* key, int32_t len, uint32_t seed) { |
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.
Check the comment: modify from https://github.com/aappleby/smhasher/blob/master/src/MurmurHash3.cpp
Why modify the origin code in the past? Is the modified method the same as murmur_hash3_x86_32?
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.
The modified method is the same as murmur_hash3_x86_32, just different in returning value.
yiguolei
left a comment
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.
LGTM
Also delete duplicated code for murmur_hash3_32
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...