You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/01/24 20:01:15 UTC
[jira] [Commented] (MAPREDUCE-4959) bundling classpath into jar
manifest on Windows does not expand environment variables or wildcards
[ https://issues.apache.org/jira/browse/MAPREDUCE-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561863#comment-13561863 ]
Chris Nauroth commented on MAPREDUCE-4959:
------------------------------------------
HADOOP-8899 added the classpath jar bundling logic to branch-1-win. YARN-316 is porting that logic to YARN on branch-trunk-win. While working on the YARN port, I discovered these issues with handling of environment variables and wildcards. The YARN-316 patch will handle these cases for YARN. I'm filing this jira to backport the same logic to branch-1-win.
> bundling classpath into jar manifest on Windows does not expand environment variables or wildcards
> --------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4959
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4959
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 1-win
> Reporter: Chris Nauroth
>
> To support long classpaths on Windows, the class path entries get bundled into a small temporary jar with a manifest that has a Class-Path attribute. When a classpath is specified in a jar manifest like this, it does not expand environment variables (i.e. %HADOOP_COMMON_HOME%), and it does not expand wildcards (i.e. lib/*.jar).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira