[
https://issues.apache.org/jira/browse/HBASE-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750696#action_12750696
]
Jonathan Gray commented on HBASE-1790:
--------------------------------------
Changed to a different example for SkipFilter, ran myself in circles with the
one that was there :) Thanks for review andrew.
Made CompareFilter abstract. Moved CompareOp to CompareFilter. Added new
classes to HOW.
Not sure what to do about HBC. Definitely agree we should not instantiate new
ones in serialization. I'm open to whatever will work :)
> 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
> Assignee: Jonathan Gray
> Fix For: 0.20.0, 0.21.0
>
> Attachments: 1790-3.patch, HBASE-1790-v2.patch, HBASE-1790-v4.patch,
> HBASE-1790-v5.patch, hbase-1790.patch, testfilter.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.
