You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org> on 2011/06/04 00:49:47 UTC
[jira] [Assigned] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
[ https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhuwanti Vaidya reassigned HBASE-3951:
----------------------------------------
Assignee: Madhuwanti Vaidya
> 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