Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <7868619.3421272266852837.JavaMail.jira@thor>
Date: Mon, 26 Apr 2010 03:27:32 -0400 (EDT)
From: "Vinod K V (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-1612) job conf file is not accessible
 from job history web page
In-Reply-To: <2010418360.368611269020907771.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod K V updated MAPREDUCE-1612:
---------------------------------

    Status: Open  (was: Patch Available)

Patch looks good. +1.

TestJobACLs is because of MAPREDUCE-1727.

Giong to commit this. Will rerun through Hudson to be sure.

> job conf file is not accessible from job history web page
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-1612
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1612
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.22.0
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>             Fix For: 0.22.0
>
>         Attachments: jobconf_history_jsp.fix.20S.patch, MR-1619-1.patch
>
>
> Clicking on conf file link from job history web page is causing an NPE if history file(and the job conf file) are stored on DFS. This NPE is from jobconf_history.jsp because jobConf built from path on DFS is not having any properties.

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