Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/13847
The performance of `hashCode()` should be pretty good in this case, and
this implementation is inline with the ones used in all other `Unsafe*` objects
(MurMurHash). I'd rather be consistent. If this turns out to be a problem, we
could always use the first n bytes (similar to the `Vector.hashCode`) for
hashCode(), if it turns out to be a problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
