Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 12 Oct 2017 13:55:00 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13108915.1507816494000.40378.1507816500780@Atlassian.JIRA>
In-Reply-To: <JIRA.13108915.1507816494000@Atlassian.JIRA>
References: <JIRA.13108915.1507816494000@Atlassian.JIRA> <JIRA.13108915.1507816494845@jira-lw-us.apache.org>
Subject: [jira] [Created] (AMBARI-22219) Set current_version for Backward
 Compatibility
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 12 Oct 2017 13:55:06 -0000

Jonathan Hurley created AMBARI-22219:
----------------------------------------

             Summary: Set current_version for Backward Compatibility
                 Key: AMBARI-22219
                 URL: https://issues.apache.org/jira/browse/AMBARI-22219
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 2.6.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Blocker
             Fix For: 2.6.0


Some stacks, mpacks, and extension services may have been relying on the deprecated and removed {{hostLevelParams/current_version}}. Although this value was removed since there is no longer a single version for the cluster, we can continue to set it using the version of the repository associated with the current command.

This will allow existing mpacks and services which were relying on this value to continue to using it until they can switch over to {{componentVersionMapping}} structure. 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)