Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 14 Apr 2015 14:50:12 +0000 (UTC)
From: "Dmitry Lysnichenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12820833.1429023008000.81521.1429023012907@Atlassian.JIRA>
In-Reply-To: <JIRA.12820833.1429023008000@Atlassian.JIRA>
References: <JIRA.12820833.1429023008000@Atlassian.JIRA>
 <JIRA.12820833.1429023008049@arcas>
Subject: [jira] [Created] (AMBARI-10467) UPGRADE: Due to changes in Ambari
 API some response validations should be allowed with warning message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Dmitry Lysnichenko created AMBARI-10467:
-------------------------------------------

             Summary: UPGRADE: Due to changes in Ambari API some response validations should be allowed with warning message
                 Key: AMBARI-10467
                 URL: https://issues.apache.org/jira/browse/AMBARI-10467
             Project: Ambari
          Issue Type: Improvement
          Components: ambari-server
            Reporter: Dmitry Lysnichenko
            Assignee: Dmitry Lysnichenko
             Fix For: 2.1.0, 2.0.1


upgradeHelper use well old realization of curl via shell execute. And to handle response errors use some kind of validation of response. For new releases of Ambari response content could be changed from time to time. We need to add some "soft" validation without generation error and just warn user about unexpected response.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)