Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 5 Oct 2015 17:54:27 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12901568.1443615049000.28056.1444067667387@Atlassian.JIRA>
In-Reply-To: <JIRA.12901568.1443615049000@Atlassian.JIRA>
References: <JIRA.12901568.1443615049000@Atlassian.JIRA>
 <JIRA.12901568.1443615049959@arcas>
Subject: [jira] [Updated] (HBASE-14524) Short-circuit comparison of rows in
 CellComparator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-14524:
--------------------------
    Attachment: HBASE-14524.patch

> Short-circuit comparison of rows in CellComparator
> --------------------------------------------------
>
>                 Key: HBASE-14524
>                 URL: https://issues.apache.org/jira/browse/HBASE-14524
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Lars Francke
>            Assignee: Lars Francke
>            Priority: Minor
>         Attachments: HBASE-14524.patch, HBASE-14524.patch
>
>
> {{CellComparator#compareRows}} compares two rows. For Scans and Gets these objects can sometimes be exactly the same object.
> I see this (without fully understanding everything that's going on) for the first cell in each row.
> In these circumstances I think it makes sense to short-circuit the comparison (not do a byte comparison and class cast checks) and bail out early if the objects are identical.


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