[jira] [Commented] (AMBARI-22219) Set current_version for Backward Compatibility

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-22219:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #375 (See [https://builds.apache.org/job/Ambari-branch-2.6/375/])
AMBARI-22219 - Set current_version for Backward Compatibility (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a1f8e9fe59eaeaade2a508518b7abb8e3a009556])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java


> 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
>
>         Attachments: AMBARI-22219.patch
>
>
> 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)