[
https://issues.apache.org/jira/browse/HBASE-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008138#comment-15008138
]
Elliott Clark commented on HBASE-14824:
---------------------------------------
We can't change an already released api like that. If anything we should just
be moving to using encoded name everywhere.
> HBaseAdmin.mergeRegions should use full region names instead of encoded
> region names
> ------------------------------------------------------------------------------------
>
> Key: HBASE-14824
> URL: https://issues.apache.org/jira/browse/HBASE-14824
> Project: HBase
> Issue Type: Bug
> Reporter: Eungsop Yoo
> Priority: Minor
> Attachments: HBASE-14824.patch
>
>
> HBaseAdmin.mergeRegions() calls HBaseAdmin.getRegion() internally.
> HBaseAdmin.getRegion() requires the full region name. So
> MetaTableAccessor.getRegion always returns null and this causes one more meta
> table scan.
> {code}
> Pair<HRegionInfo, ServerName> getRegion(final byte[] regionName) throws
> IOException {
> if (regionName == null) {
> throw new IllegalArgumentException("Pass a table name or region name");
> }
> Pair<HRegionInfo, ServerName> pair =
> MetaTableAccessor.getRegion(connection, regionName);
> if (pair == null) {
> {code}
> I suppose to use full region names instead of encoded region names in
> HBaseAdmin.mergeRegions().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
