[
https://issues.apache.org/jira/browse/AMBARI-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517603#comment-14517603
]
Hudson commented on AMBARI-10786:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2462 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2462/])
AMBARI-10786. Rename of ambari_sequences.sequence_value handled inappropriately
during Upgrade.(vbrodetskyi) (vbrodetskyi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bd62bf9a33356216c4d2b386a61c1b24210c2258)
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java
> Rename of ambari_sequences.sequence_value handled inappropriately during
> Upgrade
> --------------------------------------------------------------------------------
>
> Key: AMBARI-10786
> URL: https://issues.apache.org/jira/browse/AMBARI-10786
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10786.patch
>
>
> It seems ambari_sequences.sequence_value was renamed in 1.7.0 but 1.5.0,
> 1.6.0 and 1.6.1 Catalogs all expect column name to be sequence_value
> The rename should be idempotent, this code is doomed to fail even when
> running upgrade command more than once.
> org.apache.ambari.server.upgrade.UpgradeCatalog170#renameSequenceValueColumnName
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
