[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107953#comment-13107953
 ] 

Jeffrey Naisbitt commented on MAPREDUCE-2726:
---------------------------------------------

@Vinod:
First, we're not actually masking the /conf servlet since this code is going 
through the default /yarn route (and will therefore be at /yarn/conf).

Second, it seems weird to associate the AppMaster's /conf servlet with the job 
itself (even though right now there is basically a 1-to-1 mapping) - /conf is 
still technically the configuration for the AppMaster itself.  Additionally, 
the JobHistory won't work in this way anyway.  So, I would prefer to find a 
common and consistent way to handle the job config in both the AppMaster and 
the JobHistory (perhaps adding a /conf-xml or maybe looking at making it more 
REST-like and having some ability to specify whether you want XML or HTML).  
Therefore, I would prefer to file a separate Jira for adding links and support 
for getting the actual XML (and leave this patch as is).  What do you think?

> MR-279: Add the jobFile to the web UI
> -------------------------------------
>
>                 Key: MAPREDUCE-2726
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2726
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>            Reporter: Jeffrey Naisbitt
>            Assignee: Jeffrey Naisbitt
>            Priority: Blocker
>             Fix For: 0.23.0, 0.24.0
>
>         Attachments: MAPREDUCE-2726.patch, MAPREDUCE-2726.patch
>
>
> MAPREDUCE:2716 adds the jobfile information to the ApplicationReport.  With 
> that information available, we should add the jobfile to the web UI as well.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to