[
https://issues.apache.org/jira/browse/AMBARI-21549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096719#comment-16096719
]
Hadoop QA commented on AMBARI-21549:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12878358/AMBARI-21549.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11837//console
This message is automatically generated.
> Ambari upgrade should update unique constraints
> -----------------------------------------------
>
> Key: AMBARI-21549
> URL: https://issues.apache.org/jira/browse/AMBARI-21549
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-21549.patch
>
>
> When upgrading Ambari from 2.2.2 to 2.5 it was discovered that if a unique
> constraint is modified between Ambari versions, then we do not update the
> unique constraint.
> For example:
> *Ambari 2.2.2*
> https://github.com/apache/ambari/blob/branch-2.2.2/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L661
> {code}
> ALTER TABLE users ADD CONSTRAINT UNQ_users_0 UNIQUE (user_name, ldap_user);
> {code}
> *Ambari-2.4.0*
> https://github.com/apache/ambari/blob/branch-2.4/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql#L288
> {code}
> CONSTRAINT UNQ_users_0 UNIQUE (user_name, user_type))
> {code}
> Whenever after upgrading from Ambari 2.2.2 to Ambari 2.5.0, the unique
> constraint is not updated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
