You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by Ian Jackson <Ia...@trilliumsoftware.com> on 2013/11/22 19:20:09 UTC
Windows - Separating etc (config) from bin
It would be nice if HADOOP_CONF_DIR could be set in the environment like YARN_CONF_DIR. This could be done in lib-exec\hadoop_config.cmd by setting HADOOP_CONF_DIR conditionally.
if not defined HADOOP_CONF_DIR (
set HADOOP_CONF_DIR=%HADOOP_HOME%\etc\hadoop
)
A similar change might be done in hadoop-config.sh
Thus the bin could be under Program Files, and Program File be locked down from modification, but the configuration files still would be in a separate director.
(--config didn't seem to work for namenode)
Re: Windows - Separating etc (config) from bin
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Ian,
This sounds like a good idea. Please feel free to file a Jira for it.
Arpit
On Fri, Nov 22, 2013 at 10:20 AM, Ian Jackson <
Ian_Jackson@trilliumsoftware.com> wrote:
> It would be nice if HADOOP_CONF_DIR could be set in the environment like
> YARN_CONF_DIR. This could be done in lib-exec\hadoop_config.cmd by setting
> HADOOP_CONF_DIR conditionally.
>
> if not defined HADOOP_CONF_DIR (
>
> set HADOOP_CONF_DIR=%HADOOP_HOME%\etc\hadoop
>
> )
>
>
>
> A similar change might be done in hadoop-config.sh
>
>
>
> Thus the bin could be under Program Files, and Program File be locked down
> from modification, but the configuration files still would be in a separate
> director.
>
>
>
> (--config didn’t seem to work for namenode)
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Windows - Separating etc (config) from bin
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Ian,
This sounds like a good idea. Please feel free to file a Jira for it.
Arpit
On Fri, Nov 22, 2013 at 10:20 AM, Ian Jackson <
Ian_Jackson@trilliumsoftware.com> wrote:
> It would be nice if HADOOP_CONF_DIR could be set in the environment like
> YARN_CONF_DIR. This could be done in lib-exec\hadoop_config.cmd by setting
> HADOOP_CONF_DIR conditionally.
>
> if not defined HADOOP_CONF_DIR (
>
> set HADOOP_CONF_DIR=%HADOOP_HOME%\etc\hadoop
>
> )
>
>
>
> A similar change might be done in hadoop-config.sh
>
>
>
> Thus the bin could be under Program Files, and Program File be locked down
> from modification, but the configuration files still would be in a separate
> director.
>
>
>
> (--config didn’t seem to work for namenode)
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Windows - Separating etc (config) from bin
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Ian,
This sounds like a good idea. Please feel free to file a Jira for it.
Arpit
On Fri, Nov 22, 2013 at 10:20 AM, Ian Jackson <
Ian_Jackson@trilliumsoftware.com> wrote:
> It would be nice if HADOOP_CONF_DIR could be set in the environment like
> YARN_CONF_DIR. This could be done in lib-exec\hadoop_config.cmd by setting
> HADOOP_CONF_DIR conditionally.
>
> if not defined HADOOP_CONF_DIR (
>
> set HADOOP_CONF_DIR=%HADOOP_HOME%\etc\hadoop
>
> )
>
>
>
> A similar change might be done in hadoop-config.sh
>
>
>
> Thus the bin could be under Program Files, and Program File be locked down
> from modification, but the configuration files still would be in a separate
> director.
>
>
>
> (--config didn’t seem to work for namenode)
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Windows - Separating etc (config) from bin
Posted by Arpit Agarwal <aa...@hortonworks.com>.
Ian,
This sounds like a good idea. Please feel free to file a Jira for it.
Arpit
On Fri, Nov 22, 2013 at 10:20 AM, Ian Jackson <
Ian_Jackson@trilliumsoftware.com> wrote:
> It would be nice if HADOOP_CONF_DIR could be set in the environment like
> YARN_CONF_DIR. This could be done in lib-exec\hadoop_config.cmd by setting
> HADOOP_CONF_DIR conditionally.
>
> if not defined HADOOP_CONF_DIR (
>
> set HADOOP_CONF_DIR=%HADOOP_HOME%\etc\hadoop
>
> )
>
>
>
> A similar change might be done in hadoop-config.sh
>
>
>
> Thus the bin could be under Program Files, and Program File be locked down
> from modification, but the configuration files still would be in a separate
> director.
>
>
>
> (--config didn’t seem to work for namenode)
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.