Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 16 May 2013 01:57:15 +0000 (UTC)
From: "chunhui shen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12646512.1367965168309.329025.1368669435721@arcas>
In-Reply-To: <JIRA.12646512.1367965168309@arcas>
References: <JIRA.12646512.1367965168309@arcas>
Subject: [jira] [Commented] (HBASE-8504) HTable.getRegionsInRange() should
 provide a non-cached API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

chunhui shen commented on HBASE-8504:
-------------------------------------

Patch seems good,

but I think scanning the META will be better if not use the cache
                
> HTable.getRegionsInRange() should provide a non-cached API
> ----------------------------------------------------------
>
>                 Key: HBASE-8504
>                 URL: https://issues.apache.org/jira/browse/HBASE-8504
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client
>    Affects Versions: 0.94.7
>            Reporter: Alan Choi
>            Assignee: Matteo Bertozzi
>         Attachments: HBASE-8504-v0.patch
>
>
> getRegionsInRange() calls getRegionLocation() without reloading it. It will return wrong result if the cache is outdated due to region split. If the cost of always reloading isn't significant, we should consider doing that by default. Otherwise, let's have an API for getRegionsInRange() that forces a reload.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira