hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3416) For intra-row scanning, the update readers notification resets the query matcher and can lead to incorrect behavior
Date Wed, 02 Feb 2011 15:51:29 GMT

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

stack commented on HBASE-3416:
------------------------------

+1 We do this all over the place to get a test in.  When we rewrite it all, we'll do it so
you don't have to do such hackery.

> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message