[
https://issues.apache.org/jira/browse/HBASE-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Solomon Duskis updated HBASE-12029:
-----------------------------------
Attachment: HBASE-12029_v5.patch
{quote}
... is the new method getAllRegionLocations a replacement for
getRegionLocations? (It makes use of it...Its the preferred way going forward?)
If so, should the @deprecated have a note added that points folks to the new
method?
{quote}
Given the deprecation comments and the amount of time getRegionLocations() is
used, it does look like there's a need for a replacement. I took a shot at a
possible alternative. I added the note. Do you think that
getAllRegionLocations() is appropriate for mapreduce jobs?
metaScanner is now closed.
Removed the odd additions to RegionLocator. I replaced the RegionLocator calls
with calls to Admin in RegionSizeCalculator.
> Use Table and RegionLocator in HTable.getRegionLocations()
> -----------------------------------------------------------
>
> Key: HBASE-12029
> URL: https://issues.apache.org/jira/browse/HBASE-12029
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 0.99.1
> Reporter: Solomon Duskis
> Assignee: Solomon Duskis
> Attachments: HBASE-12029.patch, HBASE-12029_v1.patch,
> HBASE-12029_v2.patch, HBASE-12029_v3.patch, HBASE-12029_v4.patch,
> HBASE-12029_v4.patch, HBASE-12029_v5.patch
>
>
> HTable.getRegionLocations() is an internal deprecated API. There are plenty
> of internal uses of the method, and it would be ideal to use the Table and
> RegionLocator interfaces instead of the HTable method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
