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

Ramya Sunil commented on HADOOP-7779:
-------------------------------------

Agreed that its a lot cleaner but not really useful for the following reasons:

* For cases where users want to include a jar in classpath by checking if one 
already exists or not, one has to manually traverse each and every directory 
just to locate the jar.  
* We have also had cases when jobs fail due to ClassNotFoundException. A quick 
check for this would be to see whether the corresponding jar is included/not in 
the "hadoop classpath" In the current case, the wildcards wont be of much help 
unless the user is ready to recursively check every directory. IMO, the idea of 
exposing "hadoop classpath" was to let users learn about all the jars included 
in the classpath. Masking that by just printing wildcards would not serve the 
purpose.
* Also, this was the behavior in hadoop-0.20.x. I would not want to change this 
behavior unless we agree to introduce a regression.
                
> bin/hadoop classpath CLI does not display the complete classpath
> ----------------------------------------------------------------
>
>                 Key: HADOOP-7779
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7779
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Ramya Sunil
>             Fix For: 0.23.0
>
>
> bin/hadoop classpath does not display the complete classpath. The classpath 
> looks like:
> {noformat}
> $HADOOP_CONF_DIR:$HADOOP_COMMON_HOME/libexec/../share/hadoop/common/lib/*:$HADOOP_COMMON_HOME/libexec/../share/hadoop/common/*:/$HADOOP_HDFS_HOME/share/hadoop/hdfs:$HADOOP_HDFS_HOME/share/hadoop/hdfs/lib/*:$HADOOP_HDFS_HOME/share/hadoop/hdfs/*
> {noformat}
> The jar names have to be expanded instead of "*" to display the complete 
> classpath.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to