Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 2 Sep 2011 19:29:10 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1451329190.11856.1314991750139.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <719660872.41875.1313512779897.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4206) jenkins hash implementation uses
 longs unnecessarily
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096227#comment-13096227 ] 

stack commented on HBASE-4206:
------------------------------

Patch looks good to me.  Lots of changes though.  Before integrating, how do we know your changes have not changed how the hash engine works?  Thanks Ron.

> jenkins hash implementation uses longs unnecessarily
> ----------------------------------------------------
>
>                 Key: HBASE-4206
>                 URL: https://issues.apache.org/jira/browse/HBASE-4206
>             Project: HBase
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.90.4
>            Reporter: Ron Yang
>            Priority: Minor
>             Fix For: 0.92.0, 0.90.5
>
>         Attachments: ryang.patch
>
>
> I don't believe you need to use long for a,b,c and as a result no longer need to & against INT_MASK.
> At a minimum the private static longs should be made final, and the "main" method should not print the absolute value of the hash but instead use something like Integer.toHexString

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira