Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sat, 1 Oct 2011 22:30:34 +0000 (UTC)
From: "Arpit Gupta (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1074848866.730.1317508234595.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <26450169.12464.1317408705667.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7708) config generator does not update
 the properties file if on exists already
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arpit Gupta commented on HADOOP-7708:
-------------------------------------

Does it make sense to make the option to replace an existing file or not behave the same for all files not just some specific files?

May be we can take an input from the user whether he wants to replace the configs or not? That way he only gets the new config files?
                
> config generator does not update the properties file if on exists already
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-7708
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7708
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.20.205.1
>            Reporter: Arpit Gupta
>            Assignee: Eric Yang
>         Attachments: HADOOP-7708.patch
>
>
> We are copying configs to the hadoop conf dir but are not using the -f option. This leads to conf file not getting replaced in case the file exists and thus the user never gets the new conf.

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