Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <105413144.1220431664666.JavaMail.jira@brutus>
Date: Wed, 3 Sep 2008 01:47:44 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4017) Unify  the way job history filename
 is parsed
In-Reply-To: <758463425.1219689464550.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627934#action_12627934 ] 

Amar Kamat commented on HADOOP-4017:
------------------------------------

The way job details are recovered from the jobhistory filename is buggy. Every piece of code that tries to infer this information does  something like
{code}
1. split on '_'
2) username = split[5].
{code}
But the username can also have a '_' and this trick might no longer work. Same is true for jobname. 

> Unify  the way job history filename is parsed
> ---------------------------------------------
>
>                 Key: HADOOP-4017
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4017
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>
> Job history filename has the following meta-info :
> - jobtracker's hostname
> - job id
> - username
> - jobname
> {{HistoryViewer.java}} and {{jobhistory.jsp}} are required to parse the history filename to extract the meta-info. It makes more sense to provide a common utility in {{JobHistory}} to do it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.