[
https://issues.apache.org/jira/browse/MAPREDUCE-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847504#action_12847504
]
Ravi Gummadi commented on MAPREDUCE-1612:
-----------------------------------------
loadResource(Path) in Configuration.java is assuming that only paths that can
come to this method can be on local file system. But jobconf_history.jsp sends
Path that is there on DFS causing this NPE. As it is assuming the path to be
local file system, looks like fixing Configuration.java seems to be not
possible.
Regarding getting job view ACLs from history file: As getting job view ACLs
from conf file is also going to DFS twice(once for loading the JobConf, and one
more time for passing it to the xml formatter), getting job view ACLs from
history file also seems reasonable. Also, since jobconf_history.jsp is the only
JSP that is currently getting ACLs from conf file and every other history
related JSP is getting the ACLs from history file itself, making this change
would make things consistent also.
> 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
>
>
> 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.
