You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Eungsop Yoo (JIRA)" <ji...@apache.org> on 2015/11/17 06:06:10 UTC
[jira] [Updated] (HBASE-14824) HBaseAdmin.mergeRegions should use
full region names instead of encoded region names
[ https://issues.apache.org/jira/browse/HBASE-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eungsop Yoo updated HBASE-14824:
--------------------------------
Attachment: HBASE-14824.patch
> 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.
> {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)