You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Swapnil Daingade (JIRA)" <ji...@apache.org> on 2015/03/31 04:25:54 UTC
[jira] [Resolved] (HADOOP-11777) `hadoop classpath` behaviour
different from previous releases
[ https://issues.apache.org/jira/browse/HADOOP-11777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Daingade resolved HADOOP-11777.
---------------------------------------
Resolution: Duplicate
Fix Version/s: 2.7.0
Fixed as part of HDFS-7591
> `hadoop classpath` behaviour different from previous releases
> -------------------------------------------------------------
>
> Key: HADOOP-11777
> URL: https://issues.apache.org/jira/browse/HADOOP-11777
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Swapnil Daingade
> Assignee: Swapnil Daingade
> Fix For: 2.7.0
>
>
> In 2.6 doing a `hadoop classpath` returns the following
> classpath [--glob|--jar <path>|-h|--help] :
> Prints the classpath needed to get the Hadoop jar and the required
> libraries.
> Options:
> --glob expand wildcards
> --jar <path> write classpath as manifest in jar named <path>
> -h, --help print help
> This is different from earlier releases.
> However, passing any argument to the command will return the classpath as earlier
> E.g. `hadoop classpath foo`
> It would be nice to preserve the original behaviour for scripts that read the classpath using this command.
> The fix seems to be a one line change in
> hadoop-common-project/hadoop-common/src/main/bin/hadoop
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)