[
https://issues.apache.org/jira/browse/AMBARI-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-3672:
------------------------------------
Attachment: AMBARI-3672.patch
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ....................................... SUCCESS [0.078s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [0.028s]
[INFO] Ambari Web ........................................ SUCCESS [6.520s]
[INFO] Ambari Server ..................................... SUCCESS [9:01.610s]
[INFO] Ambari Agent ...................................... SUCCESS [12.029s]
[INFO] Ambari Client ..................................... SUCCESS [0.463s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
> Add Support to AmbariManagementController to derive configs from Config groups
> ------------------------------------------------------------------------------
>
> Key: AMBARI-3672
> URL: https://issues.apache.org/jira/browse/AMBARI-3672
> Project: Ambari
> Issue Type: Task
> Components: controller
> Affects Versions: 1.4.2
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.4.3
>
> Attachments: AMBARI-3672.patch
>
>
> Application of the configurations boils down to figuring out the configs for
> a Service Host Component when a Task is to be created for the host. Rules to
> apply configuration changes:
> - Apply cluster desired configs
> - Get all the config groups for the host
> - Apply the overrides per config type. (In future this can go through config
> groups for service then component and host component in that order)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
