ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-6531) Config attributes should be propagated to and persisted by Ambari agents
Date Thu, 17 Jul 2014 22:58:05 GMT
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)

Mime
View raw message