[
https://issues.apache.org/jira/browse/OOZIE-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450219#comment-15450219
]
Robert Kanter commented on OOZIE-2632:
--------------------------------------
I would also add that even if it takes a long time to run, there's a few things
to consider:
- [~gezapeti]'s point that the blobs making using DB tools
problematic/complicated
- I'm sure users would rather have an automated simple tool that takes a while
rather than an unsupported complicated manual process that might be faster
- I think the main usecase of this tool would be for migrating off of Derby,
which
-- will start running into scaling problems before it gets big enough where
this tool will take _that_ long
-- doesn't have great tools. AFAIK, there's been a few suggested ways of
migrating Oozie data out of Derby, but they've all been very hacky and don't
always work 100%
- Migrating the Oozie DB isn't going to be a common operation. It's something
that most users won't even ever do. I'd say it's better to have an easy
process for this, even if it's slow, than no process at all. As it stands now,
users typically have to loose all of their Oozie history and running
Coordinators if they need to migrate; something they're not happy about.
If we need to improve the speed, we can look into making this multithreaded
(though probably not for Derby). But that's something to save for a future
JIRA.
> 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)
