[ https://issues.apache.org/jira/browse/HADOOP-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472718#comment-13472718 ]
Hadoop QA commented on HADOOP-8899: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12548456/HADOOP-8899.branch-1-win.classpath.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1591//console This message is automatically generated. > 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