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 "Ravi Prakash (JIRA)" <ji...@apache.org> on 2015/07/30 22:58:05 UTC
[jira] [Commented] (HADOOP-10903) Enhance hadoop classpath command
to expand wildcards or write classpath into jar manifest.
[ https://issues.apache.org/jira/browse/HADOOP-10903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648298#comment-14648298 ]
Ravi Prakash commented on HADOOP-10903:
---------------------------------------
It seems like wildcards aren't *truly* supported. For e.g. if I want to include {{/pathA/pathB/pathC/someJar1-v1.2.3.jar}} and added {{/pathA/pathB/pathC/someJar1-*.jar}} to HADOOP_CLASSPATH, the output of {{hadoop classpath --glob}} still contains {{/pathA/pathB/pathC/someJar1-*.jar}} . To include what I wanted to include, I have to add {{/pathA/pathB/pathC/*}} to HADOOP_CLASSPATH. Could someone please confirm?
> Enhance hadoop classpath command to expand wildcards or write classpath into jar manifest.
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-10903
> URL: https://issues.apache.org/jira/browse/HADOOP-10903
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts, util
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: 2.6.0
>
> Attachments: HADOOP-10903.1.patch
>
>
> The "hadoop classpath" shell command currently prints the classpath variable established by the shell scripts and then exits. A few enhancements to this command would be desirable to support a few other use cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)