[
https://issues.apache.org/jira/browse/HBASE-16296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401158#comment-15401158
]
Lars Hofhansl commented on HBASE-16296:
---------------------------------------
Yeah... That's what I wanted to start the discussion on. :)
I think FilterList shouldn't add any logic that should either be in the wrapped
filter(s) itself or in HRegion. But it *is* a change. Not for any of the
Filters we have (I think) but folks could conceivably have written their own
filters and relied on this.
[~ram_krish] is the scenario you outline in TestFilterList? (sorry can't check
right now)
[~apurtell] any opinions on 0.98.
What about the other releases [~mantonov], [~busbey], [~enis], [~ndimiduk].
{{FilterList}} is {{public}} and {{stable}}.
> 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.txt, 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)
