[
https://issues.apache.org/jira/browse/OOZIE-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450279#comment-15450279
]
Peter Bacsko commented on OOZIE-2632:
-------------------------------------
An example of a migration process right now:
http://blog.shmuma.ru/2014/04/07/how-to-migrate-oozie-from-derby-to-mysql-an-easy-way/
We tried this out a couple of months ago and it didn't work - as [~gezapeti]
mentioned, BLOB fields were screwed up and coordinator jobs failed to start up
properly. I think we also had to modify the {{sed}} command to have proper SQL
syntax (and even without modification, having to run a command like this it's
simply risky).
The proposed code is very easy to read and maintain, all DB details are hidden.
Even if it's slower than using more direct methods/tools, it's very reliable.
> Provide database dump/load functionality to make database migration easier
> --------------------------------------------------------------------------
>
> Key: OOZIE-2632
> URL: https://issues.apache.org/jira/browse/OOZIE-2632
> Project: Oozie
> Issue Type: New Feature
> Reporter: Peter Cseh
> Assignee: Peter Cseh
> Attachments: OOZIE-2632.001.patch, OOZIE-2632.002.patch,
> OOZIE-2632.003.patch
>
>
> When there is a need to change the database under Oozie one has to submit all
> the workflows again or migrate the data manually which is not easy because of
> the binary blobs stored in the DB.
> oozie-setup.sh could have a db export/import command that would save the
> contents of the Db to a file and read it back from it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
