[
https://issues.apache.org/jira/browse/HBASE-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543234#comment-13543234
]
Mikhail Bautin commented on HBASE-6562:
---------------------------------------
This does not seem to be a problem with lazy seek, this is a problem with the
multi-column Bloom filter optimization (although that could be considered a
"second-level lazy seek").
The result of createLastOnRowCol should also have timestamp=MINIMUM_TIMESTAMP,
so it might be safer to check for the
combination of minimum type/timestamp. Another solution might be to pass a flag
to requestSeek to indicate that the multi-column Bloom filter optimization
should also be disabled when doing the initial seek.
> 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, 6562-v4.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
