[
https://issues.apache.org/jira/browse/HBASE-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012735#comment-15012735
]
Hudson commented on HBASE-14824:
--------------------------------
SUCCESS: Integrated in HBase-1.3 #378 (See
[https://builds.apache.org/job/HBase-1.3/378/])
HBASE-14824 HBaseAdmin.mergeRegions should recognize both full region (tedyu:
rev a6e0ad636a01e6c6595435811a18363975c24474)
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAdmin1.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java
> 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)
