Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 18 May 2015 09:06:01 +0000 (UTC)
From: "Aleksandr Maksymenko (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12830619.1431939921000.142260.1431939961348@Atlassian.JIRA>
In-Reply-To: <JIRA.12830619.1431939921000@Atlassian.JIRA>
References: <JIRA.12830619.1431939921000@Atlassian.JIRA>
 <JIRA.12830619.1431939921105@arcas>
Subject: [jira] [Created] (HBASE-13704) Hbase throws
 OutOfOrderScannerNextException exception when MultiRowRangeFilter is used.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksandr Maksymenko created HBASE-13704:
--------------------------------------------

             Summary: Hbase throws OutOfOrderScannerNextException exception when MultiRowRangeFilter is used.
                 Key: HBASE-13704
                 URL: https://issues.apache.org/jira/browse/HBASE-13704
             Project: HBase
          Issue Type: Bug
          Components: Client
    Affects Versions: 1.1.0
            Reporter: Aleksandr Maksymenko


When using filter MultiRowRangeFilter with ranges closed to each other that there are no rows between ranges, then OutOfOrderScannerNextException is throwed.
In filterRowKey method when range is switched to the next range, currentReturnCode is set to SEEK_NEXT_USING_HINT (MultiRowRangeFilter: 118 in v1.1.0). But if new range is already contain this row, then we should include this row, not to seek for another one.
Replacing line 118 to this code seems to be working fine:
{code}
if (range.contains(buffer, offset, length)) {
    currentReturnCode = ReturnCode.INCLUDE;
} else {
    currentReturnCode = ReturnCode.SEEK_NEXT_USING_HINT;
}
{code}


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