ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21549) Ambari upgrade should update unique constraints
Date Thu, 27 Jul 2017 13:03:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103181#comment-16103181
] 

Dmitry Lysnichenko commented on AMBARI-21549:
---------------------------------------------

Committed to trunk
To https://git-wip-us.apache.org/repos/asf/ambari.git
   c516b31078..b1c67d97e2  trunk -> trunk

Waiting for 2.6 branch 

> 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
>    Affects Versions: 2.5.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.6.0
>
>         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)

Mime
View raw message