[
https://issues.apache.org/jira/browse/HBASE-16296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402205#comment-15402205
]
Lars Hofhansl commented on HBASE-16296:
---------------------------------------
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.
I do not really care that much how we fix it, as long as it gets fixed. I made
two proposals now and verified that either of them fix the issue. Ted's
suggestion seems fine as long as it fixes the perf problem.
> Reverse scan performance degrades when scanner cache size matches page filter
> size
> ----------------------------------------------------------------------------------
>
> Key: HBASE-16296
> URL: https://issues.apache.org/jira/browse/HBASE-16296
> Project: HBase
> Issue Type: Bug
> Reporter: James Taylor
> Attachments: 16296-MAYBE-v2.txt, 16296-MAYBE.txt, 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)
