[
https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-5079:
--------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed (One line change that improves a random function -- hard to write
unit tests for). Thanks for the patch Jonathan.
> HashFunction inadvertently destroys some randomness
> ----------------------------------------------------
>
> Key: HADOOP-5079
> URL: https://issues.apache.org/jira/browse/HADOOP-5079
> Project: Hadoop Core
> Issue Type: Bug
> Components: util
> Reporter: Jonathan Ellis
> Assignee: stack
> Fix For: 0.20.0
>
> Attachments: hadoop-core-hash.patch
>
>
> HashFunction.hash restricts initval for the next hash to the [0, maxValue)
> range of the hash indexes returned. This is suboptimal, particularly for
> larger nbHash and smaller maxValue. Rather we should first set initval, then
> restrict the range for the result assignment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
