hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11013) CLASSPATH handling should be consolidated, debuggable
Date Thu, 28 Aug 2014 15:36:08 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer updated HADOOP-11013:
--------------------------------------

    Attachment: HADOOP-11013-01.patch

-01:

* Replaced all of the if's with a function
* Added more messages that fill in some of the blanks (e.g., when does HADOOP_NAMENODE_OPTS
get added?)
* Because I'm never happy, even with my own code

> 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
>         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)

Mime
View raw message