hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4959) bundling classpath into jar manifest on Windows does not expand environment variables or wildcards
Date Tue, 23 Jul 2013 20:04:49 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated MAPREDUCE-4959:
-------------------------------------

    Target Version/s: 1-win, 1.3.0  (was: 1-win)

Expanding scope of target versions to include next unreleased 1.x version, 1.3.0.  HBase and
others would benefit from having this code in branch-1, as per discussion on YARN-358.

[~ndimiduk], you mentioned needing this in 1.1.x.  Would it be acceptable for HBase to upgrade
to 1.3.0 to pick up this change, or would it really need to be a new 1.1.x version?
                
> 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

Mime
View raw message