[
https://issues.apache.org/jira/browse/HBASE-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664931#comment-13664931
]
Hudson commented on HBASE-8504:
-------------------------------
Integrated in HBase-TRUNK #4138 (See
[https://builds.apache.org/job/HBase-TRUNK/4138/])
HBASE-8504 HTable.getRegionsInRange() should provide a non-cached API
(Revision 1485540)
Result = SUCCESS
mbertozzi :
Files :
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> 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
> Fix For: 0.98.0, 0.95.2, 0.94.9
>
> Attachments: HBASE-8504-v0.patch, 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
