[
https://issues.apache.org/jira/browse/MAPREDUCE-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183044#comment-13183044
]
Thomas Graves commented on MAPREDUCE-3299:
------------------------------------------
Can you explain why its confusing? To get task attempts you go to
/jobs/{jobid}/tasks/{taskid}/attempts. The way REST apis work is generally you
have a resource and then you would have everything that applies/owned by that
resource. In this case the resource is a job and you are getting the job
attempts. a job also has tasks, which also have attempts which is where you
get /jobs/{jobid}/tasks/{taskid}/attempts. There are other job things like
/jobs/{jobid}/counters/, jobs/{jobid}/conf, would you prefer those have job in
front of them also?
Note - I have no strong objects to changing, just want to understand and
perhaps see if same things applies elsewhere.
> Add AMInfo table to the AM job page
> -----------------------------------
>
> Key: MAPREDUCE-3299
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3299
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Assignee: Jonathan Eagles
> Priority: Minor
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3299.patch, MAPREDUCE-3299.patch,
> MAPREDUCE-3299.patch, MAPREDUCE-3299.patch, MAPREDUCE-3299.patch,
> MAPREDUCE-3299.patch, MAPREDUCE-3299.patch
>
>
> JobHistory has a table to list all AMs. A similar table can be added to the
> AM for info on past failed AMs and the current running one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
