You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/05/02 03:44:07 UTC

[jira] [Resolved] (HBASE-12413) Mismatch in the equals and hashcode methods of KeyValue

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

Andrew Purtell resolved HBASE-12413.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.1
                   1.2.0
                   1.0.2
                   0.98.13
                   0.94.28

Pushed everywhere 0.98+. Ran TestKeyValue on all of them first. A bunch of units from 0.98 came back ok already and anyway I can't argue with that logic either.

> Mismatch in the equals and hashcode methods of KeyValue
> -------------------------------------------------------
>
>                 Key: HBASE-12413
>                 URL: https://issues.apache.org/jira/browse/HBASE-12413
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>            Priority: Minor
>             Fix For: 2.0.0, 0.94.28, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
>         Attachments: HBASE-12413-0.98.patch, HBASE-12413-V2.diff, HBASE-12413.diff, HBASE-12413.v3.patch, HBASE-12413.v4.patch, HBASE-12413.v4.patch
>
>
> In the equals method of KeyValue only row key is compared, and in the hashcode method all bacing bytes are calculated. This breaks the Java rule.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)