[
https://issues.apache.org/jira/browse/HADOOP-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267746#comment-14267746
]
Hudson commented on HADOOP-11058:
---------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2017 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2017/])
HADOOP-11058. Missing HADOOP_CONF_DIR generates strange results (Masatake
Iwasaki via aw) (aw: rev cd7d78914cd2929e42b5a893769acefdd2ed6451)
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* hadoop-common-project/hadoop-common/src/main/bin/hadoop-functions.sh
> 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
> Fix For: 3.0.0
>
> 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)
