[
https://issues.apache.org/jira/browse/HBASE-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543441#comment-13543441
]
Ted Yu commented on HBASE-6562:
-------------------------------
I agree that patches I posted didn't solve the problem.
For trunk patch, shall we introduce counterpart to the following method in
Filter ?
{code}
abstract public boolean hasFilterRow();
{code}
Namely:
{code}
abstract public boolean hasFilterRowKey();
{code}
We can then narrow !scan.hasFilter() to (!scan.hasFilter() ||
!scan.getFilter().hasFilterRowKey()).
> Fake KVs are sometimes passed to filters
> ----------------------------------------
>
> Key: HBASE-6562
> URL: https://issues.apache.org/jira/browse/HBASE-6562
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: 6562-0.94-v1.txt, 6562-0.96-v1.txt, 6562.txt,
> 6562-v2.txt, 6562-v3.txt, 6562-v4.txt, 6562-v5.txt, minimalTest.java
>
>
> In internal tests at Salesforce we found that fake row keys sometimes are
> passed to filters (Filter.filterRowKey(...) specifically).
> The KVs are eventually filtered by the StoreScanner/ScanQueryMatcher, but the
> row key is passed to filterRowKey in RegionScannImpl *before* that happens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
