You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2011/01/25 05:40:43 UTC
[jira] Updated: (HBASE-3416) For intra-row scanning, the update
readers notification resets the query matcher and can lead to incorrect
behavior
[ https://issues.apache.org/jira/browse/HBASE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-3416:
----------------------------------
Attachment: HBASE-3416.patch
First stab at the problem. All existing unit tests pass. Need also a test of intra row scanning with reader change to confirm.
> For intra-row scanning, the update readers notification resets the query matcher and can lead to incorrect behavior
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-3416
> URL: https://issues.apache.org/jira/browse/HBASE-3416
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.90.0
> Reporter: Jonathan Gray
> Fix For: 0.90.1
>
> Attachments: HBASE-3416.patch
>
>
> In {{StoreScanner.resetScannerStack()}}, which is called on the first {{next()}} call after readers have been updated, we do a query matcher reset. Normally this is not an issue because the query matcher does not need to maintain state between rows. However, if doing intra-row scanning w/ the specified limit, we could have the query matcher reset in the middle of reading a row. This could lead to incorrect behavior (too many versions coming back, etc).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.