Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 4 Mar 2015 04:18:05 +0000 (UTC)
From: "Shuaifeng Zhou (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12778108.1425003319000.72027.1425442685334@Atlassian.JIRA>
In-Reply-To: <JIRA.12778108.1425003319000@Atlassian.JIRA>
References: <JIRA.12778108.1425003319000@Atlassian.JIRA>
 <JIRA.12778108.1425003319349@arcas>
Subject: [jira] [Commented] (HBASE-13122) Improve efficiency for return
 codes of some filters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Shuaifeng Zhou commented on HBASE-13122:
----------------------------------------

NEXT_ROW can work is because there is regionscanner and store scanner, next_row affect store scanner. 
When one storescanner switch to next row, the region scanner switch to the next storescanner, the second store scanner will continue check the current row. That why the change can be more efficiency.

> Improve efficiency for return codes of some filters
> ---------------------------------------------------
>
>                 Key: HBASE-13122
>                 URL: https://issues.apache.org/jira/browse/HBASE-13122
>             Project: HBase
>          Issue Type: Improvement
>          Components: Filters
>    Affects Versions: 0.94.24, 1.0.1, 0.98.10.1
>            Reporter: Shuaifeng Zhou
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: 13122-master.patch, 13122.patch
>
>
> ColumnRangeFilter:
>  when minColumnInclusive is false, it means all the cells at the current row&column not fit the condition, so it should skip to next column, return code should be NEXT_COL, not SKIP.
> FamilyFilter is the similar sitution.
> Currently, SKIP will not causing error, but not efficent.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)