[
https://issues.apache.org/jira/browse/HBASE-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542752#comment-13542752
]
Lars Hofhansl commented on HBASE-6562:
--------------------------------------
Every filter that implements filterRowKey (including custom filters) is subject
to this.
It's only a problem with the first seek. It seems the first seek should always
be an eager seek, so that we know the real startKey (rather than the one
provided by the scan, which only needs to sort before the actual first key
scanned).
> 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.txt, 6562-v2.txt, 6562-v3.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
