[
https://issues.apache.org/jira/browse/HBASE-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748961#action_12748961
]
Clint Morgan commented on HBASE-1790:
-------------------------------------
We use filters (mostly FilterList and ValueFilter) on 0.20 to answer AND/OR
type criteria. Not much use of staful filters except as needed in ValueFilter.
For prefixing/start/stop rows we adjust the Scan.
For paging, we use a wrapper on the Scan which skips over the first results
then stops scanning after pageNum results. I realize thats not ideal as we
unnecessarily pay transport on the first skipped rows, then pay the cost to get
the N+1 row. I'd love to see PageFilter working!
> 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.
