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

Hudson commented on AMBARI-13591:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3729 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3729/])
AMBARI-13591. RU and EU: Allow set-current to force a version into the (ncole: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=81c608f4896828411871f7874168bff2e8bdb84b])
* ambari-server/src/main/python/ambari-server.py
* ambari-server/src/main/python/ambari_server/serverUpgrade.py
* ambari-server/src/test/python/TestServerUpgrade.py
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostVersionDAO.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostComponentDesiredStateDAO.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterVersionDAO.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostComponentStateDAO.java


> RU & EU: Allow set-current to force a version into the db
> ---------------------------------------------------------
>
>                 Key: AMBARI-13591
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13591
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-13591.patch
>
>
> {{ambari-server --set-current}} should have an additional option to set a 
> version to current.  Existing functionality takes the information passed in 
> and calls the Finalize action.  This attempts to go through the framework and 
> "cleanly" make sure all the versions are correct by applying the same logic 
> as finalize.
> Add a {{--force}} option to do the db work directly without going through the 
> finalize action.  If work is small enough, possible backport to 2.1.3.



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

Reply via email to