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/10/10 15:54:45 UTC

[jira] [Updated] (AMBARI-3494) UI optimization: control configurations loading

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

Andrii Tkach updated AMBARI-3494:
---------------------------------

    Attachment: AMBARI-3494.patch

> UI optimization: control configurations loading
> -----------------------------------------------
>
>                 Key: AMBARI-3494
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3494
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3494.patch
>
>
> In different places configs are loaded for some types(core-site, mapred-site, etc.), The idea is to store them into localdb. On first load we check if there is configs for this type if no then request server and put them into localdb, otherwise check the whether tags version have changed, if so then request server as well, in rest cases we load configs from local storage. Also preserve advanced configs, since they immutable we need to load them only one time. To implement this: create configController in global controllers dir and operate storing, requesting, verifying configs via that controller.



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