Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 4 Mar 2016 10:31:40 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12946946.1457087353000.4439.1457087500798@Atlassian.JIRA>
In-Reply-To: <JIRA.12946946.1457087353000@Atlassian.JIRA>
References: <JIRA.12946946.1457087353000@Atlassian.JIRA>
 <JIRA.12946946.1457087353150@arcas>
Subject: [jira] [Updated] (HBASE-15396) Enhance mapreduce.TableSplit to add
 encoded region name
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J updated HBASE-15396:
----------------------------
    Attachment: HBASE-15396.patch

> 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
>         Attachments: 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
(v6.3.4#6332)