You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2015/05/07 11:56:01 UTC

[jira] [Updated] (AMBARI-10786) Rename of ambari_sequences.sequence_value handled inappropriately during Upgrade

     [ https://issues.apache.org/jira/browse/AMBARI-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko updated AMBARI-10786:
----------------------------------------
    Attachment: AMBARI-10786.patch

> 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, 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)