Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Sat, 22 Oct 2011 02:52:32 +0000 (UTC)
From: "vitthal (Suhas) Gogate (Assigned) (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: 
 <1333357400.4219.1319251952142.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <231708666.4217.1319251832344.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (AMBARI-97) Synchronize concurrent updates to
 cluster definition and stack configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

vitthal (Suhas) Gogate reassigned AMBARI-97:
--------------------------------------------

    Assignee: vitthal (Suhas) Gogate
    
> Synchronize concurrent updates to cluster definition and stack configuration
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-97
>                 URL: https://issues.apache.org/jira/browse/AMBARI-97
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 0.1.0
>            Reporter: vitthal (Suhas) Gogate
>            Assignee: vitthal (Suhas) Gogate
>
> Updating the entity like cluster definition or stack configuration (blueprint), should require user to get the latest revision of the entity and then supply the same in the update operation. Mean time, if the latest revision of that entity has changed in the controller (due to update by other user), then current update should fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira