[ 
https://issues.apache.org/jira/browse/HADOOP-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254876#comment-14254876
 ] 

Masatake Iwasaki commented on HADOOP-11058:
-------------------------------------------

We do not need to change the code for finding conf dir by hadoop-env.sh in 
order to move HADOOP-10879 forward. It is only for backward compatibility.

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

Reply via email to