[
https://issues.apache.org/jira/browse/HBASE-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551860#comment-14551860
]
Hudson commented on HBASE-13704:
--------------------------------
SUCCESS: Integrated in HBase-1.1 #493 (See
[https://builds.apache.org/job/HBase-1.1/493/])
HBASE-13704 Hbase throws OutOfOrderScannerNextException when
MultiRowRangeFilter is used (Aleksandr Maksymenko) (tedyu: rev
ebdd45be85344b24fb2fdc5349e58e97193b6b8d)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestMultiRowRangeFilter.java
*
hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultiRowRangeFilter.java
> Hbase throws OutOfOrderScannerNextException 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
> Assignee: Aleksandr Maksymenko
> Fix For: 2.0.0, 1.2.0, 1.1.1
>
> Attachments: 13704-v1.txt
>
>
> 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)
