[jira] [Commented] (HBASE-8504) HTable.getRegionsInRange() should provide a non-cached API

["Ted Yu (JIRA)" <ji...@apache.org>]

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

Ted Yu commented on HBASE-8504:
-------------------------------

The new API may look like this ?
{code}
   * @param startKey Starting row in range, inclusive
   * @param endKey Ending row in range, exclusive
   * @param reload true to reload information or false to use cached information
   * @return A list of HRegionLocations corresponding to the regions that
   * contain the specified range
   * @throws IOException if a remote or network exception occurs
   */
  public List<HRegionLocation> getRegionsInRange(final byte [] startKey,
    final byte [] endKey, boolean reload) throws IOException {
{code}
                
> 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