[
https://issues.apache.org/jira/browse/HBASE-16296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407121#comment-15407121
]
Nick Dimiduk commented on HBASE-16296:
--------------------------------------
{quote}
The key point of my message is that {{new FilterList(new XYZFilter())}} should
behave identical to just {{new XYZFilter()}}. Right now it's not, because
FilterList has this weird logic in FilterRowKey - and perhaps other stuff. In
my opinion that is a bug.
{quote}
Sounds about right. Thanks for distilling it for us :)
> Reverse scan performance degrades when using filter lists
> ---------------------------------------------------------
>
> Key: HBASE-16296
> URL: https://issues.apache.org/jira/browse/HBASE-16296
> Project: HBase
> Issue Type: Bug
> Components: Filters
> Reporter: James Taylor
> Assignee: Ted Yu
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 0.98.21, 1.2.3
>
> Attachments: 16296-MAYBE-v2.txt, 16296-MAYBE.txt, 16296-ted-0.98.txt,
> HBASE-16296-0.98.patch, HBASE-16296-0.98.patch, HBASE-16296.patch,
> PAgefilter.patch, generatedata-snippet.java, repro-snippet.java
>
>
> When a reverse scan is done, the server seems to not know it's done when the
> scanner cache size matches the number of rows in a PageFilter. See
> PHOENIX-3121 for how this manifests itself. We have a standalone, pure HBase
> API reproducer too that I'll attach (courtesy of [~churromorales] and
> [~mujtabachohan]).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
