ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-5211) Cleanup foreign key contraints after upgrade
Date Tue, 25 Mar 2014 20:06:14 GMT

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

Mahadev konar resolved AMBARI-5211.
-----------------------------------

    Resolution: Fixed

> Cleanup foreign key contraints after upgrade
> --------------------------------------------
>
>                 Key: AMBARI-5211
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5211
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> *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)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message