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/08/28 17:50:53 UTC

[jira] Commented: (HBASE-1790) filters are not working correctly

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

stack commented on HBASE-1790:
------------------------------

Matus: Any chance of unit tests?  Please add a patch for stateful filters.  As to whether folks are using filters, the answer must be no... or at least not in any seriious way.

> filters are not working correctly
> ---------------------------------
>
>                 Key: HBASE-1790
>                 URL: https://issues.apache.org/jira/browse/HBASE-1790
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: filters
>    Affects Versions: 0.20.0, 0.21.0
>            Reporter: Matus Zamborsky
>             Fix For: 0.20.0
>
>         Attachments: hbase-1790.patch
>
>
> Filters used in Scanning the table are not working correctly. For example a table with three rows:
> 1. rowkey = adminbackslash-nb0, desc:temp = "temp"
> 2. rowkey = adminbackslash-nb1, desc:temp = "temp"
> 3. rowkey = adminkleptoman, desc:temp = "temp"
> If I scan all rows in the table without filter I get all the rows as expected. But applying a simple prefixfilter with parameter "adminbackslash" will return only first row. I searched it down to HRegion::nextInternal method, which will not output one passed row before denied row(by filter). 

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