You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/07/13 20:11:15 UTC

[jira] Resolved: (HBASE-1649) ValueFilter may not reset its internal state

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

stack resolved HBASE-1649.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.20.0
     Hadoop Flags: [Reviewed]

Reviewed and made sure our TestVF passed.

Thanks for the patch Doğacan.  Good stuff.

> ValueFilter may not reset its internal state
> --------------------------------------------
>
>                 Key: HBASE-1649
>                 URL: https://issues.apache.org/jira/browse/HBASE-1649
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: filters
>    Affects Versions: 0.20.0
>            Reporter: Doğacan Güney
>            Priority: Minor
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1649.patch
>
>
> ValueFilter#reset is empty even though the class uses two internal variables. These values are reset in filterRow, however there are instances where filterRow may not be called. For example, if you chain two filters through FilterList (with PASS_ALL and the second filter being a ValueFilter) then during FilterList#filterRow if the first filter#filterRow returns true then ValueFilter#filterRow will not be called.

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