ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18609) Implement a way to configure Stack Upgrade Merger to skip particular properties to be merged from stack defaults
Date Tue, 18 Oct 2016 14:55:58 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Onischuk updated AMBARI-18609:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk

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

Mime
View raw message