hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16296) Reverse scan performance degrades when scanner cache size matches page filter size
Date Mon, 01 Aug 2016 05:19:20 GMT

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

ramkrishna.s.vasudevan commented on HBASE-16296:
------------------------------------------------

{code}
       if (isFilterDoneInternal()) {
4311	          return false;
4312	        }
{code}
Should work for filterList case. But for single filter this will not work. 
It will go ahead with the the previous existing way. (so no problem).
So in order to avoid even that and for changing the behaviour of FilterList I think its better
we return filterRowKey based on filterAllRemaining.  
In the sense if filterAllRemaining is true then filterRowKey should also be true. 


> 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, 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)

Mime
View raw message