You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2016/02/22 23:25:18 UTC

[jira] [Commented] (MAPREDUCE-6640) mapred job -history command should be able to take Job ID

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

Robert Kanter commented on MAPREDUCE-6640:
------------------------------------------

Not sure why Jenkins didn't run for this.  I've manually kicked it off now.

> mapred job -history command should be able to take Job ID
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-6640
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6640
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: MAPREDUCE-6640.001.patch
>
>
> The {{mapred job -history}} command currently accepts only a {{jobHistoryFile>}}.  It would be much easier for the user if it could also accept a Job ID so the user doesn't have to go and find the jhist file.  It would also be more consistent with the other commands, which generally take a Job ID.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)