Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1311267266.1224837704201.JavaMail.jira@brutus>
Date: Fri, 24 Oct 2008 01:41:44 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (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:all-tabpanel ]

Amar Kamat updated HADOOP-4017:
-------------------------------

    Attachment: HADOOP-4017-v1.1.patch

A small bug fixed.

> 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
>            Assignee: Amar Kamat
>         Attachments: HADOOP-4017-v1.1.patch, HADOOP-4017-v1.patch
>
>
> 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.