[jira] [Resolved] (MAPREDUCE-123) HistoryViewer usage string is misleading.

["nijel (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nijel resolved MAPREDUCE-123.
-----------------------------
    Resolution: Implemented

Hi,

The command usage string is changed
{code} 
master:/home/nijel/hadoop-3.0.0-SNAPSHOT/bin # ./hadoop job -history
WARNING: Use of this script to execute job is deprecated.
WARNING: Attempting to execute replacement "mapred job" instead.

Usage: "job [-history <jobHistoryFile>"]
master:/home/nijel/hadoop-3.0.0-SNAPSHOT/bin #

{code}

Closing the issue as implemented. 
Please reopen if you feel more analysis required

> HistoryViewer usage string is misleading.
> -----------------------------------------
>
>                 Key: MAPREDUCE-123
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-123
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>
> $ hadoop job -history
> Usage: JobClient [-history <jobOutputDir>]
> The input is actually a history-location (for e.g., specified by hadoop.job.history.user.location) which happens to default to a jobOutputDir. The usage string should reflect this.
> Also the restriction for history files to be in a _logs/history sub-directory is stringent. This could be changed so that history can be directly put in hadoop.job.history.user.location similar to how we store directly in hadoop.job.history.location. Seems like _logs/history is only intended to be used in conjuction with jobOutputDir, as a default location.



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