[
https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044120#comment-13044120
]
Madhuwanti Vaidya commented on HBASE-3951:
------------------------------------------
One part of this was fixed by HBASE-3416. setRow is also called in
StoreScanner.next.
> ScanQueryMatcher::setRow is not always being called on a row transition.
> ------------------------------------------------------------------------
>
> Key: HBASE-3951
> URL: https://issues.apache.org/jira/browse/HBASE-3951
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Madhuwanti Vaidya
> Assignee: Madhuwanti Vaidya
> Priority: Minor
> Attachments: TestScanBatch.java
>
>
> When a scan is used with a batch, setRow is called on the same row within
> each call to next. Since setRow resets deletes, the result set contains kvs
> that should have been suppressed by a delete.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
