hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Lawlor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13193) RegionScannerImpl filters should not be reset if a partial Result is returned
Date Mon, 16 Mar 2015 22:03:38 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364056#comment-14364056

Jonathan Lawlor commented on HBASE-13193:

Ran the failing test (TestSplitTransactionOnCluster) three times locally with the patch applied
to branch-1 and all test runs passed. Failure seems unrelated.

> RegionScannerImpl filters should not be reset if a partial Result is returned
> -----------------------------------------------------------------------------
>                 Key: HBASE-13193
>                 URL: https://issues.apache.org/jira/browse/HBASE-13193
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jonathan Lawlor
>            Assignee: Jonathan Lawlor
>             Fix For: 2.0.0, 1.1.0
>         Attachments: HBASE-13193-v1.patch, HBASE-13193-v2.patch, HBASE-13193-v3.patch,
HBASE-13193-v4.patch, HBASE-13193-v4.patch, HBASE-13193-v4.patch, HBASE-13193-v5.patch
> In RegionScannerImpl the filters get reset during calls to nextRaw:
> {code}
> public NextState nextRaw(List<Cell> outResults, int batchLimit, long remainingResultSize)
>         throws IOException {
>   ...
>   resetFilters();
>   if (isFilterDoneInternal()) {
>   ...
> }
> {code}
> This creates a problem when returning partial Results because filters should only be
reset in between rows (i.e. after all of the cells for a particular row have been returned).
If a partial Result is returned, there are still cells in the row that have not been evaluated
yet and we should avoid resetting the filter since it will wipe away all state information
for that filter.

This message was sent by Atlassian JIRA

View raw message