[
https://issues.apache.org/jira/browse/HBASE-16296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399258#comment-15399258
]
Lars Hofhansl commented on HBASE-16296:
---------------------------------------
While I'm still at the airport waiting for my flight... So is the FilterList
logic incorrect - or at least unnecessary? Why would we filterRowKey only
because a filter in the list has filterAllRemaining? If the filter wished to
exhibit this behavior it could (and should) do so itself.
> 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: 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)
