[
https://issues.apache.org/jira/browse/MAPREDUCE-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-6640:
-------------------------------------
Attachment: MAPREDUCE-6640.002.patch
The 002 patch:
- Fixed the extra import Karthik mentioned. The exit code defaults to -1, so
there's no need to explicitly set it for the use case you mentioned; it's done
implicitly.
- fixes checkstyle other than the "Redundant 'public' modifier." ones in
{{JobReport}} to be consistent with the existing code, the "More than 7
parameters" ones in {{JobStatus}} because that's how many arguments there are,
and the "Method length is 388 lines" one in {{CLI}} because that's just how
long it is
- fixes related unit test failures ({{TestJobHistoryEntities}} and
{{TestJobInfo}})
> 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)
