ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-2290) Ambari Upgrade prcoess should preserve the old configs and add the new config options to the old config files.
Date Wed, 05 Jun 2013 15:56:22 GMT

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

Dmitry Lysnichenko commented on AMBARI-2290:
--------------------------------------------

+1
                
> Ambari Upgrade prcoess should preserve the old configs and add the new config options
to the old config files.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-2290
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2290
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.5
>            Reporter: Dmitry Sen
>            Assignee: Dmitry Sen
>            Priority: Critical
>             Fix For: 1.2.5
>
>         Attachments: AMBARI-2290.patch
>
>
> The Ambari Upgrade process should preserve the old configs and add the new config options
to the old config files.
> Currently we have it the other way around, that we copy the needed 3 properties from
the old config files - this is wrong. We need to use the older config file and add the new
options to the old config file. This is because the older config file can have all kinds of
config option that the user might have used. We have to really really keep in mind usability
of the product when fixing issues.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message