You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "ryan rawson (JIRA)" <ji...@apache.org> on 2009/06/23 04:28:07 UTC

[jira] Commented: (HBASE-1568) Client doesnt consult old row filter interface in filterSaysStop() - could result in NPE or excessive scanning

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

ryan rawson commented on HBASE-1568:
------------------------------------

testing on my cluster this seems to fix the issues i was seeing.

we should have a test :-)

> Client doesnt consult old row filter interface in filterSaysStop() - could result in NPE or excessive scanning
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1568
>                 URL: https://issues.apache.org/jira/browse/HBASE-1568
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: filters
>    Affects Versions: 0.20.0
>            Reporter: ryan rawson
>            Assignee: ryan rawson
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1568.patch
>
>
> The implementation of HTable.ClientScanner.filterSaysStop() doesnt refer to the old filter, which could result in an NPE if you use an old-style filter.
> It also ignores the old style filter, so if you want to use old filters only, you dont get the effect you need.

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