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

Jason Lowe commented on HADOOP-8604:
------------------------------------

The conf/ directory within the Hadoop tree is intended to hold the 
sample/default configuration.  During development, custom configuration changes 
are not intended to be placed in that directory, as those changes will be 
overwritten during builds.  Usually custom configuration is placed in a 
separate directory, outside the Hadoop tree, and conveyed to Hadoop via the 
HADOOP_CONF_DIR environment variable.  You can also specify a config directory 
via the --config option to the hadoop front-end script.  With a separate config 
directory, your changes won't be overwritten during compilation.
                
> conf/* files overwritten at Hadoop compilation
> ----------------------------------------------
>
>                 Key: HADOOP-8604
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8604
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 1.0.3
>            Reporter: Robert Grandl
>            Priority: Minor
>
> Whenever I compile hadoop from terminal as:
> ant compile jar run
> all the conf/* files are overwritten. I am not sure if some of them should 
> not be like that but at least hadoop-env.sh, mapred-site.ml, core-site.xml, 
> hdfs-site.xml, masters, slaves should remains. Otherwise I am forced to 
> backup and replace content again after compilation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to