[
https://issues.apache.org/jira/browse/AMBARI-21397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082571#comment-16082571
]
Hudson commented on AMBARI-21397:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1667 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1667/])
AMBARI-21397. Remove previous upgrades to allow schema change (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2b147ea66976181db82a82ec933b1186589de437])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
> Remove previous upgrades to allow schema change
> -----------------------------------------------
>
> Key: AMBARI-21397
> URL: https://issues.apache.org/jira/browse/AMBARI-21397
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21397.patch
>
>
> AMBARI-21358 introduced schema change to allow tracking upgrade between
> repository versions instead of free text "version" descriptors. Ambari
> Server upgrade currently fails because of this schema change if there are any
> previous upgrades. It's not worth trying to fix the data, and the
> repositories required for the foreign keys may not even be there anymore. So
> we should remove {{upgrade}}, all child data ({{upgrade_group}},
> {{upgrade_item}}, {{servicecomponent_history}}), and the reference from
> {{clusters}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
