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:44:13 GMT

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

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

I don't think the patch is correct. The problem is when you set the startRow of a scan to
an actually existing row key it must not be filtered out, because it will be skipped over
on next().
Also see TestFromClientSide.testJira6912, which failed in the test run.

                
> 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