hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chunhui shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8504) HTable.getRegionsInRange() should provide a non-cached API
Date Wed, 08 May 2013 02:03:15 GMT

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

chunhui shen commented on HBASE-8504:

I think the caller of HTable#getRegionsInRange should always handle the case which the cache
is outdated.
The region location may be wrong even if we get it through non-cached API because of region-move
or region-split 

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

View raw message