hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14824) HBaseAdmin.mergeRegions should recognize both full region names and encoded region names
Date Wed, 18 Nov 2015 22:25:11 GMT

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

Ted Yu updated HBASE-14824:
---------------------------
    Summary: HBaseAdmin.mergeRegions should recognize both full region names and encoded region
names  (was: HBaseAdmin.mergeRegions should use full region names instead of encoded region
names)

> 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
>            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)

Mime
View raw message