hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7708) config generator does not update the properties file if on exists already
Date Wed, 05 Oct 2011 13:26:34 GMT

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

Hudson commented on HADOOP-7708:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk #851 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/851/])
    HADOOP-7708. Fixed hadoop-setup-conf.sh to handle config file
consistently.  (Eric Yang)
HADOOP-7708. Fixed hadoop-setup-conf.sh to handle config files
consistently.  (Eric Yang)

eyang : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1178969
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/packages/hadoop-setup-conf.sh

eyang : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1178965
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/packages/hadoop-setup-conf.sh

                
> 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.0
>            Reporter: Arpit Gupta
>            Assignee: Eric Yang
>            Priority: Critical
>             Fix For: 0.20.205.0, 0.23.0
>
>         Attachments: HADOOP-7708-1.patch, HADOOP-7708-trunk-1.patch, HADOOP-7708-trunk.patch,
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

        

Mime
View raw message