[jira] [Updated] (AMBARI-6531) Config attributes should be propagated to and persisted by Ambari agents

["Srimanth Gunturi (JIRA)" <ji...@apache.org>]

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

Srimanth Gunturi updated AMBARI-6531:
-------------------------------------

    Attachment: AMBARI-6531.patch

Review at https://reviews.apache.org/r/23687/

> Config attributes should be propagated to and persisted by Ambari agents
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-6531
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6531
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.7.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-6531.patch
>
>
> When {{properties_attributes}} are set on configurations, the changes have to be propagated to and persisted by Ambari agents. 
> For example, a POST call to _core_site.xml_ 
> {code}
> {
>   "tag": "version1",
>   "type": "core-site",
>   "properties": {
>     "fs.defaultFS": "hdfs://server:8020",
>     "fs.trash.interval": "360",
>     "hadoop.proxyuser.falcon.groups": "users",
>     ...
>     "mapreduce.jobtracker.webinterface.trusted": "false"
>   },
>   “properties_attributes”: {
>     “final”: {
>      "fs.defaultFS": “true”, 
>      "hadoop.proxyuser.falcon.groups": “true”
>     },
>   }
> }
> {code}
> should be sent to agents in _ExecutionCommand_s and _StatusCommand_s. The agents should then save the final flag via the _XmlConfigProvider_.
> Tests should be made to take care of create, update and delete of final attributes on configs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)