hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (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 Thu, 03 Feb 2011 15:26:29 GMT

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

Hudson commented on HBASE-3416:
-------------------------------

Integrated in HBase-TRUNK #1731 (See [https://hudson.apache.org/hudson/job/HBase-TRUNK/1731/])
    

> 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
>            Assignee: Andrew Purtell
>             Fix For: 0.90.1, 0.92.0
>
>         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