You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/08/28 00:54:58 UTC

[jira] [Created] (HADOOP-11013) CLASSPATH handling should be considated, debuggable

Allen Wittenauer created HADOOP-11013:
-----------------------------------------

             Summary: CLASSPATH handling should be considated, debuggable
                 Key: HADOOP-11013
                 URL: https://issues.apache.org/jira/browse/HADOOP-11013
             Project: Hadoop Common
          Issue Type: Improvement
            Reporter: Allen Wittenauer


As part of HADOOP-9902, java execution across many different shell bits were consolidated down to (effectively) two routines.  Prior to calling those two routines, the CLASSPATH is exported.  This export should really be getting handled in the exec function and not in the individual shell bits.

Additionally, it would be good if there was:

{code}
echo ${CLASSPATH} > /dev/null
{code}

so that bash -x would show the content of the classpath or even a '--debug classpath' option that would echo the classpath to the screen prior to java exec to help with debugging.




--
This message was sent by Atlassian JIRA
(v6.2#6252)