[
https://issues.apache.org/jira/browse/HBASE-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418142#comment-13418142
]
Jason Dai commented on HBASE-6429:
----------------------------------
Assume we have a table as follows:
{noformat}
row1 => <f1:c1, 1_c1> , <f1:c2 , 1_c2>, <f1:c3 , 1_c3>, <f1:c4 , 1_c4>, <f1:c5
, 1_c5>
row2 => <f1:c1 , 2_c1> , <f1:c2 , 2_c2>, <f1:c3 , 2_c3>, <f1:c4 , 2_c4>, <f1:c5
, 2_c5>
{noformat}
And we scan the table using the Scan below:
{noformat}
Scan scan = new Scan();
scan.setBatch(2);
SingleColumnValueFilter filter = new
SingleColumnValueFilter(Bytes.toBytes("f1"),
Bytes.toBytes("c5"),
CompareFilter.CompareOp.EQUAL,
new SubstringComparator("2_c5"));
scan.setFilter(filter);
{noformat}
The results that we got are:
{noformat}
<f1:c1, 1_c1> , <f1:c2 , 1_c2>, <f1:c3 , 1_c3>, <f1:c4 , 1_c4>,
<f1:c1 , 2_c1> , <f1:c2 , 2_c2>, <f1:c3 , 2_c3>, <f1:c4 , 2_c4>, <f1:c5 , 2_c5>
{noformat}
which is not correct. Since we cannot ensure that the column related to the
filter criteria can be scanned with limit, an IncompatibleFilterException
should be thrown here.
> Filter with filterRow() returning true is also incompatible with scan with
> limit
> --------------------------------------------------------------------------------
>
> Key: HBASE-6429
> URL: https://issues.apache.org/jira/browse/HBASE-6429
> Project: HBase
> Issue Type: Bug
> Components: filters
> Affects Versions: 0.96.0
> Reporter: Jason Dai
>
> Currently if we scan with bot limit and a Filter with
> filterRow(List<KeyValue>) implemented, an IncompatibleFilterException will
> be thrown. The same exception should also be thrown if the filer has its
> filterRow() implemented.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
