[
https://issues.apache.org/jira/browse/AMBARI-12706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966825#comment-14966825
]
Hudson commented on AMBARI-12706:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3685 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3685/])
AMBARI-12706. Stop-and-Start Upgrade: Handle Downgrade path (dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cfb6ccd47eb48f25c236fdab3c201da84aadacf0])
*
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/stack/UpgradePack.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java
> Stop-and-Start Upgrade: Handle Downgrade path
> ---------------------------------------------
>
> Key: AMBARI-12706
> URL: https://issues.apache.org/jira/browse/AMBARI-12706
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0
>
>
> A downgrade is the exact same steps repeated so far, starting from the
> beginning. Instead of tacking backups, will have to restore DBs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
