hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6640) mapred job -history command should be able to take Job ID
Date Tue, 23 Feb 2016 22:39:18 GMT

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

Karthik Kambatla commented on MAPREDUCE-6640:
---------------------------------------------

+1

> 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, MAPREDUCE-6640.002.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)

Mime
View raw message