[AMBARI-5211] Cleanup foreign key contraints after upgrade

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.5.0
• Component/s: ambari-server
• Assignee: Papirkovskyy Myroslav
• Reporter: Papirkovskyy Myroslav
• Created: 25/Mar/14 18:01
• Updated: 25/Mar/14 20:04
• Resolved: 25/Mar/14 20:04

Description

Situation:

• We modified constraint names for foreign keys to fit Oracle restriction
• However, did not make names consistent across all DB types
• Now Upgrade java code has to have smaller length constraint names to work with Oracle
• So after upgrade there could be:
  1. More that 1 constraint for same set of columns. (Postgres)
  OR
  2. Exceptions in the logs saying cannot add a constraint. (Oracle)

Fix:

• Drop old constraints before adding new ones. (Only for the ones which are different in both CREATE sql scripts)

Issue Links

• links to: ReviewBoard