You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Grinenko (JIRA)" <ji...@apache.org> on 2016/10/17 12:49:58 UTC
[jira] [Updated] (AMBARI-18609) Implement a way to configure Stack
Upgrade Merger to skip particular properties to be merged from stack
defaults
[ https://issues.apache.org/jira/browse/AMBARI-18609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Grinenko updated AMBARI-18609:
-------------------------------------
Attachment: AMBARI-18609.patch
> Implement a way to configure Stack Upgrade Merger to skip particular properties to be merged from stack defaults
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-18609
> URL: https://issues.apache.org/jira/browse/AMBARI-18609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Dmytro Grinenko
> Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18609.patch
>
>
> We need to reincarnate on-stack-upgrade feature in less functionality way. It's true, that we don't need an analog to Stack Advisor or Upgrade Packs, however we need a way to exclude some property from being merged with stack defaults during Upgrade.
> Why we need this: there could be a lot of situations, when we need some properties only in some
> picante moments, and these properties regulated according to Stack Advisor/Wizards or another internal state. In this case, these properties shipped with dummy stack default values, which are incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)