[
https://issues.apache.org/jira/browse/HADOOP-10903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079553#comment-14079553
]
Chris Nauroth commented on HADOOP-10903:
----------------------------------------
Typically, the output of "hadoop classpath" includes wildcards, because we take
advantage of wildcard syntax to simplify our classpath. Two enhancements would
be beneficial:
# An option to print the classpath after wildcard expansion. This is helpful
for use in environments that need the classpath but don't support the wildcard
syntax. One example is libhdfs, where a common user error is incorrectly
setting the CLASSPATH environment variable with wildcards.
# An option to write the classpath into a jar file manifest. This helps work
around command line length limitations with our very long classpaths. For
example, Windows command prompt is limited to 8191 characters. We've already
used the technique of packing the classpath into a jar manifest successfully in
the YARN NodeManager.
The default behavior can still be to print the classpath calculated by the
shell scripts and then exit immediately. This is still valuable behavior for
getting a glimpse of the classpath before JVM launch, just in case the scripts
are doing something completely unexpected.
> 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
>
> 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.2#6252)
