[AMBARI-21549] Ambari upgrade should update unique constraints

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.6.0
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 21/Jul/17 14:46
• Updated: 14/Aug/17 12:26
• Resolved: 14/Aug/17 11:52

Description

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

ALTER TABLE users ADD CONSTRAINT UNQ_users_0 UNIQUE (user_name, ldap_user);

Ambari-2.4.0
https://github.com/apache/ambari/blob/branch-2.4/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql#L288

CONSTRAINT UNQ_users_0 UNIQUE (user_name, user_type))

Whenever after upgrading from Ambari 2.2.2 to Ambari 2.5.0, the unique constraint is not updated.

Issue Links

• links to: review_request_