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/03 22:26:47 UTC
[jira] [Created] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition (eg: using batching in scan), which
causes deletes to be reset and hence ignored.
ScanQueryMatcher::setRow is not always being called on a row transition (eg: using batching in scan), which causes deletes to be reset and hence ignored.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: HBASE-3951
URL: https://issues.apache.org/jira/browse/HBASE-3951
Project: HBase
Issue Type: Bug
Components: regionserver
Reporter: Madhuwanti Vaidya
Priority: Minor
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhuwanti Vaidya resolved HBASE-3951.
--------------------------------------
Resolution: Duplicate
Fix Version/s: 0.92.0
> 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
> Fix For: 0.92.0
>
> 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
[jira] [Commented] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045090#comment-13045090 ]
Madhuwanti Vaidya commented on HBASE-3951:
------------------------------------------
sorry, my bad. This part has also been fixed as part of HBASE-1537.
> 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
[jira] [Updated] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhuwanti Vaidya updated HBASE-3951:
-------------------------------------
Description:
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.
> 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
> Priority: Minor
>
> 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
[jira] [Assigned] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Work started] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HBASE-3951 started by 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
[jira] [Updated] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhuwanti Vaidya updated HBASE-3951:
-------------------------------------
Attachment: TestScanBatch.java
Unit test to demonstrate this bug.
> 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
> 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
[jira] [Updated] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhuwanti Vaidya updated HBASE-3951:
-------------------------------------
Summary: ScanQueryMatcher::setRow is not always being called on a row transition. (was: ScanQueryMatcher::setRow is not always being called on a row transition (eg: using batching in scan), which causes deletes to be reset and hence ignored. )
> 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
> Priority: Minor
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3951) ScanQueryMatcher::setRow is not
always being called on a row transition.
Posted by "Madhuwanti Vaidya (JIRA)" <ji...@apache.org>.
[ 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