[
https://issues.apache.org/jira/browse/HADOOP-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478656#comment-13478656
]
Suresh Srinivas commented on HADOOP-8899:
-----------------------------------------
Alejandro, this is manifest only jar. See similar things done in maven surefire
-
http://maven.apache.org/plugins/maven-surefire-plugin/examples/class-loading.html.
bq. then things will not work as expected as you'll lose some of those files in
the consolidation
I do not understand given above comment. All you have done is create a jar with
manifest file that has classpath. What do mean by things will not work as
expected?
> Classpath exceeds maximum OS limit
> ----------------------------------
>
> Key: HADOOP-8899
> URL: https://issues.apache.org/jira/browse/HADOOP-8899
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1-win
> Reporter: Ahmed El Baz
> Attachments: HADOOP-8899.branch-1-win.classpath.patch
>
>
> We hit errors in TT due to long classpath value. One example is Oozie trying
> to start a hive job, and it fails with the following error:
> java.io.IOException: Command exceeds the OS command length limit: 8192,
> command: "set CLASSPATH="….
> The classpath includes Hadoop Core + Hive Jars which are in the distributed
> cache. This is causing the classpath to be too long giving the error above. A
> viable long term fix is to generate a temporary JAR file in the task cache
> directory which includes all elements in the long classpath, and then provide
> this as the "-classpath" argument for the JVM to be spawned. This is gated
> for Windows only.
--
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
