You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Appy (JIRA)" <ji...@apache.org> on 2015/12/22 11:24:46 UTC
[jira] [Updated] (HBASE-14824) HBaseAdmin.mergeRegions should
recognize both full region names and encoded region names
[ https://issues.apache.org/jira/browse/HBASE-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Appy updated HBASE-14824:
-------------------------
Component/s: Admin
> HBaseAdmin.mergeRegions should recognize both full region names and encoded region names
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-14824
> URL: https://issues.apache.org/jira/browse/HBASE-14824
> Project: HBase
> Issue Type: Bug
> Components: Admin
> Reporter: Eungsop Yoo
> Assignee: Eungsop Yoo
> Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: HBASE-14824-v1.patch, HBASE-14824-v2.patch, 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)