You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2016/09/07 10:27:20 UTC
[jira] [Updated] (AMBARI-18278) Provide Notes On Service Config
Changes During Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Lysnichenko updated AMBARI-18278:
----------------------------------------
Attachment: AMBARI-18278.2.patch
> Provide Notes On Service Config Changes During Ambari Upgrade
> -------------------------------------------------------------
>
> Key: AMBARI-18278
> URL: https://issues.apache.org/jira/browse/AMBARI-18278
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18278.2.patch, AMBARI-18278.patch
>
>
> For every configuration change made, a meaningful note should be included so that administrators understand why so many versions are being created. Any of the following would be fine:
> - Ambari Upgrade updated storm-site
> - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site
> - The following configurations were changed as part of the Ambar Server Upgrade: storm-site
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)