[
https://issues.apache.org/jira/browse/HBASE-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651874#comment-13651874
]
Matteo Bertozzi commented on HBASE-8504:
----------------------------------------
I agree with [~zjushch]. Even if you have a fresh version of the locations,
between the get and your use a region may be moved.
Do you see a problem like "getRegionsInRange() cache is never invalidated after
a change" or your request is more like "I want fresher result"? because in the
second case even a fresh version may be outdated.
> 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
