hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1190) TableInputFormatBase with row filters scan too far
Date Sun, 08 Feb 2009 19:40:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew Purtell updated HBASE-1190:

       Resolution: Fixed
    Fix Version/s: 0.20.0
         Assignee: Andrew Purtell
           Status: Resolved  (was: Patch Available)

Thanks for the patch Dave! Passes all local tests, applied to trunk and 0.19 branch. 

> TableInputFormatBase with row filters scan too far 
> ---------------------------------------------------
>                 Key: HBASE-1190
>                 URL: https://issues.apache.org/jira/browse/HBASE-1190
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Dave Latham
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.19.1, 0.20.0
>         Attachments: HBASE-1190.patch
> When TableInputFormatBase has a non-null RowFilterInterface to apply, it creates combines
the row filter with a StopRowFilter to get a scanner for each input split.  However, the StopRowFilter
never indicates that fitlerAllRemaining is true, so each input split will end up scanning
to the end of the table.  (Contrast with HTable.getScanner(byte[][] columns, byte[] starRow,
byte[] stopRow, long timestamp) which uses a StopRowFilter wrapped in a WhileMatchRowFilter
to ensure that scanning ends at the stop row.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message