You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Alejandro Abdelnur (Created) (JIRA)" <ji...@apache.org> on 2011/12/08 15:30:39 UTC

[jira] [Created] (OOZIE-631) Oozie upgrade/migration tool

Oozie upgrade/migration tool
----------------------------

                 Key: OOZIE-631
                 URL: https://issues.apache.org/jira/browse/OOZIE-631
             Project: Oozie
          Issue Type: New Feature
            Reporter: Alejandro Abdelnur
            Assignee: Alejandro Abdelnur


Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.

A more generic mechanism using OpenJPA schematool should be available.

This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "Alejandro Abdelnur (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Abdelnur updated OOZIE-631:
-------------------------------------

    Description: 
By default creating Oozie database done automatically by Oozie. 

While this is convenient for developers, it is not acceptable when setting up a production system.

A tool to create the DB should be provided.

Similarly, upgrading Oozie DB should be supported by such tool.

This should work for all supported DBs.

Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.

A more generic mechanism using OpenJPA schematool should be available.

This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

  was:
Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.

A more generic mechanism using OpenJPA schematool should be available.

This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

        Summary: Oozie DB create/upgrade tool  (was: Oozie upgrade/migration tool)
    
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205682#comment-13205682 ] 

jiraposter@reviews.apache.org commented on OOZIE-631:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3838/
-----------------------------------------------------------

Review request for oozie.


Summary
-------

The ooziedb.sh command line allows to create/upgrade/check-version of an Oozie DB.

It works with all supported DBs (Oracle, MySQL, Postgres, Derby), leveraging OpenJPA mapping tool for that.

It works in 2 modes:

* sql generation only: generates the necessary scripts only
* sql generation and execution: in addition runs the scripts


This addresses bug OOZIE-631.
    https://issues.apache.org/jira/browse/OOZIE-631


Diffs
-----

  trunk/core/src/main/conf/oozie-site.xml 1242884 
  trunk/docs/src/site/twiki/AG_Install.twiki 1242884 
  trunk/docs/src/site/twiki/AG_OozieUpgrade.twiki PRE-CREATION 
  trunk/docs/src/site/twiki/DG_QuickStart.twiki 1242884 
  trunk/docs/src/site/twiki/index.twiki 1242884 
  trunk/pom.xml 1242884 
  trunk/src/main/assemblies/distro.xml 1242884 
  trunk/src/main/assemblies/tools.xml PRE-CREATION 
  trunk/tools/pom.xml PRE-CREATION 
  trunk/tools/src/main/bin/ooziedb.sh PRE-CREATION 
  trunk/tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java PRE-CREATION 

Diff: https://reviews.apache.org/r/3838/diff


Testing
-------

tested with derby/oracle/mysql/postgres DBs, both for creation and upgrades


Thanks,

Alejandro


                
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "Alejandro Abdelnur (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Abdelnur resolved OOZIE-631.
--------------------------------------

    Resolution: Fixed

Committed to trunk
                
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "Alejandro Abdelnur (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Abdelnur updated OOZIE-631:
-------------------------------------

    Fix Version/s: 3.2.0
    
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 3.2.0
>
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219801#comment-13219801 ] 

jiraposter@reviews.apache.org commented on OOZIE-631:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3838/#review5485
-----------------------------------------------------------



trunk/core/src/main/conf/oozie-site.xml
<https://reviews.apache.org/r/3838/#comment11877>

    good point, this patch is introducing this name. it seems that has not been changed when we moved to JPAService, i'll take care of renaming the property name.


- Alejandro


On 2012-02-10 19:36:46, Alejandro Abdelnur wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/3838/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-02-10 19:36:46)
bq.  
bq.  
bq.  Review request for oozie.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  The ooziedb.sh command line allows to create/upgrade/check-version of an Oozie DB.
bq.  
bq.  It works with all supported DBs (Oracle, MySQL, Postgres, Derby), leveraging OpenJPA mapping tool for that.
bq.  
bq.  It works in 2 modes:
bq.  
bq.  * sql generation only: generates the necessary scripts only
bq.  * sql generation and execution: in addition runs the scripts
bq.  
bq.  
bq.  This addresses bug OOZIE-631.
bq.      https://issues.apache.org/jira/browse/OOZIE-631
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    trunk/core/src/main/conf/oozie-site.xml 1242884 
bq.    trunk/docs/src/site/twiki/AG_Install.twiki 1242884 
bq.    trunk/docs/src/site/twiki/AG_OozieUpgrade.twiki PRE-CREATION 
bq.    trunk/docs/src/site/twiki/DG_QuickStart.twiki 1242884 
bq.    trunk/docs/src/site/twiki/index.twiki 1242884 
bq.    trunk/pom.xml 1242884 
bq.    trunk/src/main/assemblies/distro.xml 1242884 
bq.    trunk/src/main/assemblies/tools.xml PRE-CREATION 
bq.    trunk/tools/pom.xml PRE-CREATION 
bq.    trunk/tools/src/main/bin/ooziedb.sh PRE-CREATION 
bq.    trunk/tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java PRE-CREATION 
bq.  
bq.  Diff: https://reviews.apache.org/r/3838/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  tested with derby/oracle/mysql/postgres DBs, both for creation and upgrades
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Alejandro
bq.  
bq.


                
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220110#comment-13220110 ] 

jiraposter@reviews.apache.org commented on OOZIE-631:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3838/
-----------------------------------------------------------

(Updated 2012-03-01 15:49:49.093812)


Review request for oozie.


Changes
-------

Updating oozie-site.xml to use JPAService for JDBC properties.


Summary
-------

The ooziedb.sh command line allows to create/upgrade/check-version of an Oozie DB.

It works with all supported DBs (Oracle, MySQL, Postgres, Derby), leveraging OpenJPA mapping tool for that.

It works in 2 modes:

* sql generation only: generates the necessary scripts only
* sql generation and execution: in addition runs the scripts


This addresses bug OOZIE-631.
    https://issues.apache.org/jira/browse/OOZIE-631


Diffs (updated)
-----

  trunk/core/src/main/conf/oozie-site.xml 1295631 
  trunk/docs/src/site/twiki/AG_Install.twiki 1295631 
  trunk/docs/src/site/twiki/AG_OozieUpgrade.twiki PRE-CREATION 
  trunk/docs/src/site/twiki/DG_QuickStart.twiki 1295631 
  trunk/docs/src/site/twiki/index.twiki 1295631 
  trunk/pom.xml 1295631 
  trunk/src/main/assemblies/distro.xml 1295631 
  trunk/src/main/assemblies/tools.xml PRE-CREATION 
  trunk/tools/pom.xml PRE-CREATION 
  trunk/tools/src/main/bin/ooziedb.sh PRE-CREATION 
  trunk/tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java PRE-CREATION 

Diff: https://reviews.apache.org/r/3838/diff


Testing
-------

tested with derby/oracle/mysql/postgres DBs, both for creation and upgrades


Thanks,

Alejandro


                
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219762#comment-13219762 ] 

jiraposter@reviews.apache.org commented on OOZIE-631:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3838/#review5481
-----------------------------------------------------------



trunk/core/src/main/conf/oozie-site.xml
<https://reviews.apache.org/r/3838/#comment11875>

    Why the SToreService? is not it JPAService which is set in oozie-default.xml


- Mohammad


On 2012-02-10 19:36:46, Alejandro Abdelnur wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/3838/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-02-10 19:36:46)
bq.  
bq.  
bq.  Review request for oozie.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  The ooziedb.sh command line allows to create/upgrade/check-version of an Oozie DB.
bq.  
bq.  It works with all supported DBs (Oracle, MySQL, Postgres, Derby), leveraging OpenJPA mapping tool for that.
bq.  
bq.  It works in 2 modes:
bq.  
bq.  * sql generation only: generates the necessary scripts only
bq.  * sql generation and execution: in addition runs the scripts
bq.  
bq.  
bq.  This addresses bug OOZIE-631.
bq.      https://issues.apache.org/jira/browse/OOZIE-631
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    trunk/core/src/main/conf/oozie-site.xml 1242884 
bq.    trunk/docs/src/site/twiki/AG_Install.twiki 1242884 
bq.    trunk/docs/src/site/twiki/AG_OozieUpgrade.twiki PRE-CREATION 
bq.    trunk/docs/src/site/twiki/DG_QuickStart.twiki 1242884 
bq.    trunk/docs/src/site/twiki/index.twiki 1242884 
bq.    trunk/pom.xml 1242884 
bq.    trunk/src/main/assemblies/distro.xml 1242884 
bq.    trunk/src/main/assemblies/tools.xml PRE-CREATION 
bq.    trunk/tools/pom.xml PRE-CREATION 
bq.    trunk/tools/src/main/bin/ooziedb.sh PRE-CREATION 
bq.    trunk/tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java PRE-CREATION 
bq.  
bq.  Diff: https://reviews.apache.org/r/3838/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  tested with derby/oracle/mysql/postgres DBs, both for creation and upgrades
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Alejandro
bq.  
bq.


                
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-631) Oozie DB create/upgrade tool

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220380#comment-13220380 ] 

jiraposter@reviews.apache.org commented on OOZIE-631:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3838/#review5528
-----------------------------------------------------------

Ship it!


+1

- Mayank


On 2012-03-01 15:49:49, Alejandro Abdelnur wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/3838/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-03-01 15:49:49)
bq.  
bq.  
bq.  Review request for oozie.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  The ooziedb.sh command line allows to create/upgrade/check-version of an Oozie DB.
bq.  
bq.  It works with all supported DBs (Oracle, MySQL, Postgres, Derby), leveraging OpenJPA mapping tool for that.
bq.  
bq.  It works in 2 modes:
bq.  
bq.  * sql generation only: generates the necessary scripts only
bq.  * sql generation and execution: in addition runs the scripts
bq.  
bq.  
bq.  This addresses bug OOZIE-631.
bq.      https://issues.apache.org/jira/browse/OOZIE-631
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    trunk/core/src/main/conf/oozie-site.xml 1295631 
bq.    trunk/docs/src/site/twiki/AG_Install.twiki 1295631 
bq.    trunk/docs/src/site/twiki/AG_OozieUpgrade.twiki PRE-CREATION 
bq.    trunk/docs/src/site/twiki/DG_QuickStart.twiki 1295631 
bq.    trunk/docs/src/site/twiki/index.twiki 1295631 
bq.    trunk/pom.xml 1295631 
bq.    trunk/src/main/assemblies/distro.xml 1295631 
bq.    trunk/src/main/assemblies/tools.xml PRE-CREATION 
bq.    trunk/tools/pom.xml PRE-CREATION 
bq.    trunk/tools/src/main/bin/ooziedb.sh PRE-CREATION 
bq.    trunk/tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java PRE-CREATION 
bq.  
bq.  Diff: https://reviews.apache.org/r/3838/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  tested with derby/oracle/mysql/postgres DBs, both for creation and upgrades
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Alejandro
bq.  
bq.


                
> Oozie DB create/upgrade tool
> ----------------------------
>
>                 Key: OOZIE-631
>                 URL: https://issues.apache.org/jira/browse/OOZIE-631
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> By default creating Oozie database done automatically by Oozie. 
> While this is convenient for developers, it is not acceptable when setting up a production system.
> A tool to create the DB should be provided.
> Similarly, upgrading Oozie DB should be supported by such tool.
> This should work for all supported DBs.
> Currently upgrading Oozie DB is a manual process, not properly documented and the SQL scripts for it work only with Oracle.
> A more generic mechanism using OpenJPA schematool should be available.
> This could be done with a tool that would indicate if the DB needs to be upgraded, can be upgrade and upgrades/migrates it. The tool would take a currentVersion and a targetVersion of Oozie plus the JDBC information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira