hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6562) Fake KVs are sometimes passed to filters
Date Thu, 03 Jan 2013 23:00:15 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543393#comment-13543393
] 

Lars Hofhansl commented on HBASE-6562:
--------------------------------------

A KV with Type=Minimum and TS=OLDEST_TIMESTAMP is created by KeyValue.createLastOnRowCol(...)
and KeyValue.createLastOnRow(...). The former is indeed only called from StoreFileScanner.requestSeek.
The latter on the other hand is called by ScanQueryMatcher, and is used to request seeks.

                
> 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, 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

Mime
View raw message