[
https://issues.apache.org/jira/browse/OOZIE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated OOZIE-900:
--------------------------
Attachment: OOZIE-900.patch
Hey Rajesh,
Whats the harm in showing the stack-trace though? Seems helpful for debug
purposes anyway.
I've instead added a patch that enhances the output indicating it is for debug
reasons. Does this look reasonable to you?
> Don't throw an exception when db schema already exists
> ------------------------------------------------------
>
> Key: OOZIE-900
> URL: https://issues.apache.org/jira/browse/OOZIE-900
> Project: Oozie
> Issue Type: Improvement
> Components: scripts
> Reporter: Rajesh Koilpillai
> Priority: Trivial
> Attachments: OOZIE-900.patch
>
>
> If the schema already exists, just display a message instead of throwing an
> exception.
> bin/ooziedb.sh create -sqlfile oozie.sql
> Validate DB Connection
> DONE
> Check DB schema does not exist
> Error: DB schema exists
> --------------------------------------
> java.lang.Exception: DB schema exists
> at
> org.apache.oozie.tools.OozieDBCLI.validateDBSchema(OozieDBCLI.java:383)
> at org.apache.oozie.tools.OozieDBCLI.createDB(OozieDBCLI.java:168)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:112)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:63)
> --------------------------------------
--
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
