[
https://issues.apache.org/jira/browse/OOZIE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413937#comment-13413937
]
Harsh J commented on OOZIE-900:
-------------------------------
Thanks Rajesh. IMHO, we should keep it, just to know what the trace path looked
like in case there's ever an issue. We log all exceptions this way, not just
genuine thrown ones/etc., so thats how its coming to be for even expected
results.
I'd like to hear what others think. We could also booleanize the various
methods to return a fail/pass state, if expected, and an exception for other
assorted issues during the code flow.
> 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
> Affects Versions: 3.2.0
> 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
