[jira] [Commented] (OOZIE-2198) OozieDBCLI doesn't show any information on why it thinks a schema doesn't exist

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490300#comment-14490300 ] 

Hadoop QA commented on OOZIE-2198:
----------------------------------

Testing JIRA OOZIE-2198

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 132
.    {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1643
.    Tests failed: 1
.    Tests errors: 0

.    The patch failed the following testcases:

.      testCoordRerunDateNeg(org.apache.oozie.command.coord.TestCoordRerunXCommand)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2306/

> OozieDBCLI doesn't show any information on why it thinks a schema doesn't exist
> -------------------------------------------------------------------------------
>
>                 Key: OOZIE-2198
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2198
>             Project: Oozie
>          Issue Type: Improvement
>    Affects Versions: 4.1.0
>            Reporter: Ravi Prakash
>            Assignee: Ravi Prakash
>            Priority: Minor
>         Attachments: OOZIE-2198.01.patch, OOZIE-2198.02.patch
>
>
> When running ooziedb.sh upgrade, I got this error:
> {code}
> Validate DB Connection
> DONE
> Check DB schema exists
> Error: DB schema does not exist
> Stack trace for the error was (for debug purposes):
> --------------------------------------
> java.lang.Exception: DB schema does not exist
> at org.apache.oozie.tools.OozieDBCLI.validateDBSchema(OozieDBCLI.java:883)
> at org.apache.oozie.tools.OozieDBCLI.upgradeDB(OozieDBCLI.java:196)
> at org.apache.oozie.tools.OozieDBCLI.run(OozieDBCLI.java:128)
> at org.apache.oozie.tools.OozieDBCLI.main(OozieDBCLI.java:76)
> {code}
> It doesn't tell me anything about why it thinks no schema exists. We should surface the exception



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)