hbase-issues mailing list archives

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

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

Hudson commented on HBASE-8504:
-------------------------------

Integrated in hbase-0.95 #210 (See [https://builds.apache.org/job/hbase-0.95/210/])
    HBASE-8504 HTable.getRegionsInRange() should provide a non-cached API (Revision 1485541)

     Result = SUCCESS
mbertozzi : 
Files : 
* /hbase/branches/0.95/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

Mime
View raw message