Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 33735 invoked from network); 13 Feb 2009 16:35:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Feb 2009 16:35:24 -0000 Received: (qmail 58435 invoked by uid 500); 13 Feb 2009 16:35:20 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 58387 invoked by uid 500); 13 Feb 2009 16:35:20 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 58371 invoked by uid 99); 13 Feb 2009 16:35:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2009 08:35:20 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2009 16:35:19 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 8E38E234C48B for ; Fri, 13 Feb 2009 08:34:59 -0800 (PST) Message-ID: <1146191127.1234542899577.JavaMail.jira@brutus> Date: Fri, 13 Feb 2009 08:34:59 -0800 (PST) From: "stack (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-5255) Fix for HADOOP-5079 HashFunction inadvertently destroys some randomness In-Reply-To: <1246767367.1234540621490.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-5255: -------------------------- Attachment: hadoop-core-hash-2-branch-0.20.patch Jonathan Ellis patch moved over from HADOOP-5079. Fixes fact that can return negative value if hash returned is Integer.MIN_VALUE. Patch is for branch-0.20 > Fix for HADOOP-5079 HashFunction inadvertently destroys some randomness > ----------------------------------------------------------------------- > > Key: HADOOP-5255 > URL: https://issues.apache.org/jira/browse/HADOOP-5255 > Project: Hadoop Core > Issue Type: Bug > Components: io > Affects Versions: 0.20.0, 0.21.0 > Reporter: stack > Priority: Minor > Fix For: 0.20.0, 0.21.0 > > Attachments: hadoop-core-hash-2-branch-0.20.patch > > > HADOOP-5079 did this "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." The patch committed on that issue introduced a new bug: "My first patch contained a regression: you have to take the remainder before calling Math.abs, since Math.abs(Integer.MIN_VALUE) == Integer.MIN_VALUE still" (Jonathan Ellis). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.