[
https://issues.apache.org/jira/browse/MAPREDUCE-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610549#comment-14610549
]
Ray Chiang commented on MAPREDUCE-6422:
---------------------------------------
For all job/task related queries, I'd recommend being able to specify a range
of what to return (as already recommended in MAPREDUCE-3971). This has two
benefits:
1) You could break queries into smaller chunks of data. Some of the queries
would take too long otherwise.
2) This could also open the door for a more responsive web UI that isn't part
of the particular server (e.g. RM, JHS)
> Add REST API for getting all attempts for all the tasks
> -------------------------------------------------------
>
> Key: MAPREDUCE-6422
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6422
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Lavkesh Lahngir
> Assignee: Lavkesh Lahngir
>
> Web UI has the feature where one can get all attempts for all map tasks or
> reduce tasks.
> REST api seems to be missing it.
> Should we add this in both HsWebService and AMWebService ?
> {code}
> @GET
> @Path("/mapreduce/jobs/{jobid}/tasks/attempts")
> @Produces({ MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML })
> public JobTaskAttemptsInfo getAllJobTaskAttempts(@Context
> HttpServletRequest hsr,
> @PathParam("jobid") String jid, @QueryParam("type") String type) {
> }
> {code}
> We might also add queryparam on state to filter by succeeded attempts etc.
> Thoughts ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
