Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <1277183933.1243039965554.JavaMail.jira@brutus>
Date: Fri, 22 May 2009 17:52:45 -0700 (PDT)
From: "Zheng Shao (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-511) Change the hashcode for DoubleWritable
In-Reply-To: <2054835929.1243037565542.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712329#action_12712329 ] 

Zheng Shao commented on HIVE-511:
---------------------------------

Text and String are both "STRING" primitive type.
The relationship between Text and String are the same as that between IntWritable and Integer - they will have WritableStringOI and JavaStringOI, which both implements StringOI.


> Change the hashcode for DoubleWritable
> --------------------------------------
>
>                 Key: HIVE-511
>                 URL: https://issues.apache.org/jira/browse/HIVE-511
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Zheng Shao
>         Attachments: HIVE-511.1.patch
>
>
> The current DoubleWritable hashCode takes only the last 32 bits. This is a big problem because for small integer values like 1.0, 2.0, 15.0, the hashCode are all 0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.