You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2014/07/18 00:58:05 UTC
[jira] [Created] (AMBARI-6531) Config attributes should be
propagated to and persisted by Ambari agents
Srimanth Gunturi created AMBARI-6531:
----------------------------------------
Summary: 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
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)