Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Thu, 24 Jan 2013 01:32:11 +0000 (UTC)
From: "Mahadev konar (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12627702.1358274588140.182876.1358991131490@arcas>
In-Reply-To: <JIRA.12627702.1358274588140@arcas>
References: <JIRA.12627702.1358274588140@arcas>
Subject: [jira] [Commented] (AMBARI-1194) API support for cascade delete of
 a specified cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mahadev konar commented on AMBARI-1194:
---------------------------------------

+1 the patch looks good to me.
                
> API support for cascade delete of a specified cluster
> -----------------------------------------------------
>
>                 Key: AMBARI-1194
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1194
>             Project: Ambari
>          Issue Type: New Feature
>    Affects Versions: 1.2.0
>            Reporter: Yusaku Sako
>            Assignee: Tom Beerbower
>            Priority: Critical
>             Fix For: 1.3.0, 1.2.1
>
>         Attachments: AMBARI-1194.patch
>
>
> We need to be able to allow the user to reconfigure the cluster if installation fails.
> It would greatly simplify UI logic if the API supported cascade delete of the cluster (delete the cluster and all of its sub-resources).
> This way, the UI can simply issue DELETE on cluster and proceed as if performing a fresh cluster install. This minimizes code changes on the UI side to support AMBARI-1193.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira