You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/09/16 00:10:34 UTC
[jira] [Updated] (HADOOP-11013) CLASSPATH handling should be
consolidated, debuggable
[ https://issues.apache.org/jira/browse/HADOOP-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-11013:
--------------------------------------
Issue Type: New Feature (was: Improvement)
> CLASSPATH handling should be consolidated, debuggable
> -----------------------------------------------------
>
> Key: HADOOP-11013
> URL: https://issues.apache.org/jira/browse/HADOOP-11013
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Fix For: 3.0.0
>
> Attachments: HADOOP-11013-01.patch, HADOOP-11013.patch
>
>
> 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.3.4#6332)