ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-4109) Manage config-groups dialog should persist only hitting Save (installer and reconfigure)
Date Wed, 18 Dec 2013 16:56:12 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851907#comment-13851907
] 

Aleksandr Kovalenko commented on AMBARI-4109:
---------------------------------------------

committed to trunk

> Manage config-groups dialog should persist only hitting Save (installer and reconfigure)
> ----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-4109
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4109
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.3
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 1.4.3
>
>         Attachments: AMBARI-4109.patch, AMBARI-4109_branch-1.4.3.patch
>
>
> Currently in the manag-config-groups dialog, we have the left had side table that is
live (updates backend as you change), and right hand side table which updates only when you
hit {{Save}}. 
> We need all changes (add/remove/rename/duplicate config-groups, change modify config
groups) to be persisted only on hitting {{Save}}.
> For doing this we need to copy config-groups into like original-config-groups, and allow
{{Save}} only when changes happen from original-config-groups. We need to make the least number
of API calls as possible.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message