hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4959) bundling classpath into jar manifest on Windows does not expand environment variables or wildcards
Date Mon, 05 Aug 2013 21:10:47 GMT

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

Nick Dimiduk commented on MAPREDUCE-4959:
-----------------------------------------

As I consider this further, I don't think generating a temp jar is sufficient for our needs.
What we want is the hbase-manifest.jar to be created a install time, once all of the path
structures are resolved.

HBase's current minimum Hadoop version is at 1.1.2. I don't know what the future will hold.

Ping [~apurtell] for thoughts on both points.
                
> 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