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

Robert Kanter commented on OOZIE-2290:
--------------------------------------

I've seen this problem before.  I agree that we should move the version update 
to after the DDL tweaks.

This still doesn't necessarily fix issues where the upgrade runs into a problem 
part-way, and you have a partially updated database.  Simply running the db 
upgrade tool again won't always work.  Ideally, we'd make it so that if there's 
an error, it rolls back the changes as well.  Alternatively, if there's some 
way of making it so that running the db upgrade tool again somehow resumes the 
upgrade.

> Oozie db version update should happen after all DDL tweak.
> ----------------------------------------------------------
>
>                 Key: OOZIE-2290
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2290
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Bowen Zhang
>            Assignee: Bowen Zhang
>             Fix For: trunk
>
>
> Currently, if some of the DDL tweak fails, users will think the DB has 
> upgraded to a newer version since db version update happens at the front.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to