hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Bertozzi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8504) HTable.getRegionsInRange() should provide a non-cached API
Date Wed, 15 May 2013 21:25:16 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matteo Bertozzi updated HBASE-8504:

    Attachment: HBASE-8504-v0.patch

we already expose a getRegionLocation(row, reload) so I guess we can add also this one.

I assume that the use is to get the "more accurate" region location as possible at the moment
of the call. Keeping in mind that this location may be already old during the use.
> 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
>         Attachments: 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

View raw message