hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5079) HashFunction inadvertently destroys some randomness
Date Tue, 10 Feb 2009 01:54:59 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Douglas updated HADOOP-5079:
----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

Jonathan: please open a new issue to correct the regression.

>  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-2.patch, 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.


Mime
View raw message