[
https://issues.apache.org/jira/browse/HADOOP-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265382#comment-14265382
]
Allen Wittenauer commented on HADOOP-11058:
-------------------------------------------
bq. Hmm... the fact that hadoop_exec_hadoopenv and hadoop_exec_userfuncs use
the value of HADOOP_CONF_DIR before hadoop_exec_hadooprc may be confusing.
It calls that very, very minimally. Those functions use them to build up the
shell environment using any site settings. Now a user can add/modify to the
existing site level shell env. After this call, HADOOP_CONF_DIR is added to
the classpath for Java.
Looks like the wrong file was uploaded for -04....
> Missing HADOOP_CONF_DIR generates strange results
> -------------------------------------------------
>
> Key: HADOOP-11058
> URL: https://issues.apache.org/jira/browse/HADOOP-11058
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Reporter: Allen Wittenauer
> Assignee: Masatake Iwasaki
> Labels: newbie
> Attachments: HADOOP-11058.1.patch, HADOOP-11058.2.patch,
> HADOOP-11058.3.patch, HADOOP-11058.4.patch
>
>
> If HADOOP_CONF_DIR is defined but points to a directory that either doesn't
> exist or isn't actually a viable configuration directory, all sorts of weird
> things happen, especially for logging. The shell code should do a better job
> of verifying the directory is valid and exit if it detects if it is broken in
> some way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
