Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 7 May 2015 09:58:00 +0000 (UTC)
From: "Dmitry Lysnichenko (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12825513.1430224128000.34480.1430992680061@Atlassian.JIRA>
In-Reply-To: <JIRA.12825513.1430224128000@Atlassian.JIRA>
References: <JIRA.12825513.1430224128000@Atlassian.JIRA>
 <JIRA.12825513.1430224128215@arcas>
Subject: [jira] [Updated] (AMBARI-10786) Rename of
 ambari_sequences.sequence_value handled inappropriately during Upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dmitry Lysnichenko updated AMBARI-10786:
----------------------------------------
    Attachment:     (was: 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_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)