Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/3795#issuecomment-68088854
In general, it seems that it would be better not to rely on hashCode
directly in spark, but rather have some layer of indirection, similar to
nonNegativeHashCode. After all, the ordinal of an enum seems like it would
make a reasonable hash code.
On Dec 24, 2014 9:47 PM, "Apache Spark QA" <[email protected]> wrote:
> Test build #24809 has started
>
<https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24809/consoleFull>
> for PR 3795 at commit c41483d
>
<https://github.com/apache/spark/commit/c41483d035ebf3b5b20acfb244c67b8bbea24412>
> .
>
> - This patch merges cleanly.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/3795#issuecomment-68088533>.
>
---
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]
