[
https://issues.apache.org/jira/browse/HADOOP-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115261#comment-14115261
]
Hudson commented on HADOOP-11013:
---------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #1854 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1854/])
HADOOP-11013. CLASSPATH handling should be consolidated, debuggable (aw) (aw:
rev d8774cc577198fdc3bc36c26526c95ea9a989800)
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs
* hadoop-common-project/hadoop-common/src/main/bin/hadoop-functions.sh
* hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* hadoop-common-project/hadoop-common/src/main/bin/hadoop
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-common-project/hadoop-common/src/main/bin/rcc
* hadoop-mapreduce-project/bin/mapred
> CLASSPATH handling should be consolidated, debuggable
> -----------------------------------------------------
>
> Key: HADOOP-11013
> URL: https://issues.apache.org/jira/browse/HADOOP-11013
> Project: Hadoop Common
> Issue Type: Improvement
> 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.2#6252)
