You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2013/11/18 18:31:22 UTC

[jira] [Created] (AMBARI-3796) Config-groups configs should be saved efficiently

Andrii Tkach created AMBARI-3796:
------------------------------------

             Summary: Config-groups configs should be saved efficiently
                 Key: AMBARI-3796
                 URL: https://issues.apache.org/jira/browse/AMBARI-3796
             Project: Ambari
          Issue Type: Bug
          Components: client
    Affects Versions: 1.4.2
            Reporter: Andrii Tkach
            Assignee: Andrii Tkach
             Fix For: 1.4.2


Configs in config-groups get added, changed and removed. When edits are done in a non-default config-group, only the config-group should have its configs and tags updated. When default config-group is changed, the cluster level desired_configs are updated.
We should verify that add, update and removal of configs at both default and non-default config-groups work well.
Also, only the sites that were changed should be updated. For example, if I went into HDFS service and changed a config in hdfs-site.xml, we should only update 1 site/tag for that config-group. core-site.xml and global site/tag should not be updated.



--
This message was sent by Atlassian JIRA
(v6.1#6144)