hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15396) Enhance mapreduce.TableSplit to add encoded region name
Date Wed, 06 Apr 2016 19:21:25 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228930#comment-15228930

Hudson commented on HBASE-15396:

SUCCESS: Integrated in HBase-1.3-IT #598 (See [https://builds.apache.org/job/HBase-1.3-IT/598/])
HBASE-15396 Enhance mapreduce.TableSplit to add encoded region name (busbey: rev ff075fd9dfe33eaf179cff562e86949d1599c2fe)
* hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableSplit.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormatBase.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableSplit.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/MultiTableInputFormatBase.java

> Enhance mapreduce.TableSplit to add encoded region name
> -------------------------------------------------------
>                 Key: HBASE-15396
>                 URL: https://issues.apache.org/jira/browse/HBASE-15396
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>    Affects Versions: 1.3.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>         Attachments: HBASE-15396-branch-1.patch, HBASE-15396.patch, HBASE-15396.patch,
HBASE-15396.patch, HBASE-15396.patch
> When troubleshooting HBase-input MR job map failures, the TableSplit's toString() definition
comes very handy. However, it still does not tell us directly which region ID it was created
for (it does tell us the key and the host, but not the exact region name, so there's a second
lookup needed from the UI to find the ID to then check the servers with).
> It would be beneficial to have the encoded region name as part of the output, so this
extra manual lookup can be avoided. The encoded name is much easier to find events with.

This message was sent by Atlassian JIRA

View raw message