Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 8 Jan 2015 20:26:34 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12604955.1345868555000.41593.1420748794973@Atlassian.JIRA>
In-Reply-To: <JIRA.12604955.1345868555000@Atlassian.JIRA>
References: <JIRA.12604955.1345868555000@Atlassian.JIRA>
 <JIRA.12604955.1345868555389@arcas>
Subject: [jira] [Resolved] (HBASE-6664) Filter compound comparators nor
 comparator subclasses are compared properly by test code
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-6664.
--------------------------
    Resolution: Won't Fix

Closing. See Gregory's justification

> Filter compound comparators nor comparator subclasses are compared properly by test code
> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-6664
>                 URL: https://issues.apache.org/jira/browse/HBASE-6664
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: stack
>              Labels: delete
>
> Gregory over in https://reviews.apache.org/r/6670/ explains the issue.  See the comment here at https://reviews.apache.org/r/6670/diff/1/?file=142078#file142078line88  Its about when tests call areSerializedFieldsEqual to figure if objects are equal.  When its comparators, and the comparator has been subclassed or is made of multiple sub comparators, then we'll not compare right.


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