ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-10786) Rename of ambari_sequences.sequence_value handled inappropriately during Upgrade
Date Thu, 07 May 2015 12:37:59 GMT

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

Dmitry Lysnichenko updated AMBARI-10786:
----------------------------------------
    Fix Version/s: 2.0.1

> 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, 2.0.1
>
>         Attachments: AMBARI-10786.patch, AMBARI-10786_branch_branch-2.0.maint.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)

Mime
View raw message