----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51137/#review147441 -----------------------------------------------------------
Ship it! Ship It! - Robert Kanter On Aug. 31, 2016, 10:25 a.m., Peter Cseh wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/51137/ > ----------------------------------------------------------- > > (Updated Aug. 31, 2016, 10:25 a.m.) > > > Review request for oozie. > > > Bugs: OOZIE-2632 > https://issues.apache.org/jira/browse/OOZIE-2632 > > > Repository: oozie-git > > > Description > ------- > > 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. Functionality added > with some tests. The database is dumped using GSON to json files and zipped > to a single file to use less disk space. > > > Diffs > ----- > > distro/src/main/bin/oozie-setup.ps1 > ca89b8838c8f43b659605b6e4d83cdefa530c21c > distro/src/main/bin/oozie-setup.sh 3b6a6431fef007e77f3b3d99f4e98807e1808c11 > pom.xml 9e06e89fdaceb5ac53d12bef2e624f755fa7f350 > tools/pom.xml 114ba8ee8dd2d531837e2ae4097b7ea3c0419eed > tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java > 8b3e93918d595d0235090f4dafb5f04158d45398 > tools/src/main/java/org/apache/oozie/tools/OozieDBExportCLI.java > PRE-CREATION > tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java > PRE-CREATION > tools/src/test/java/org/apache/oozie/tools/TestDBLoadDump.java PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_ac.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_bna.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_bnj.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_ca.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_cj.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_slareg.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_slasum.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_sysinfo.json PRE-CREATION > tools/src/test/resources/dumpData/ooziedb_wf.json PRE-CREATION > > Diff: https://reviews.apache.org/r/51137/diff/ > > > Testing > ------- > > I've tested migrating between MySQL, Derby and Oracle. After restarting > Oozie, the workflows/coordinators kept running and their status was updated > properly. > > > Thanks, > > Peter Cseh > >
