Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 21 Sep 2016 14:50:20 +0000 (UTC)
From: "Will Murnane (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.13006520.1474469417000.627718.1474469420573@Atlassian.JIRA>
In-Reply-To: <JIRA.13006520.1474469417000@Atlassian.JIRA>
References: <JIRA.13006520.1474469417000@Atlassian.JIRA> <JIRA.13006520.1474469417806@arcas>
Subject: [jira] [Created] (ACCUMULO-4468) accumulo.core.data.Key.equals(Key,
 PartialKey) improvement
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 21 Sep 2016 14:50:22 -0000

Will Murnane created ACCUMULO-4468:
--------------------------------------

             Summary: accumulo.core.data.Key.equals(Key, PartialKey) improvement
                 Key: ACCUMULO-4468
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4468
             Project: Accumulo
          Issue Type: Improvement
          Components: core
    Affects Versions: 1.8.0
            Reporter: Will Murnane
            Priority: Trivial


In the Key.equals(Key, PartialKey) overload, the current method compares starting at the beginning of the key, and works its way toward the end. This functions correctly, of course, but one of the typical uses of this method is to compare adjacent rows to break them into larger chunks. For example, accumulo.core.iterators.Combiner repeatedly calls this method with subsequent pairs of keys.

I have a patch which reverses the comparison order. That is, if the method is called with ROW_COLFAM_COLQUAL_COLVIS, it will compare visibility, cq, cf, and finally row. This (marginally) improves the speed of comparisons in the relatively common case where only the last part is changing, with less complex code.


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