[
https://issues.apache.org/jira/browse/OOZIE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632182#comment-14632182
]
Hadoop QA commented on OOZIE-2245:
----------------------------------
Testing JIRA OOZIE-2245
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:red}-1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:red}-1{color} the patch seems to introduce 6 new javac warning(s)
{color:red}-1 BACKWARDS_COMPATIBILITY{color}
. {color:red}-1{color} the patch seems to change 1 line(s) with JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{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/2446/
> Service to periodically check database schema
> ---------------------------------------------
>
> Key: OOZIE-2245
> URL: https://issues.apache.org/jira/browse/OOZIE-2245
> Project: Oozie
> Issue Type: New Feature
> Components: core
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: OOZIE-2245.002.patch, OOZIE-2245.patch
>
>
> We've seen a number of issues related to the database schema being incorrect
> (more than you would think). It seems some users go and muck around in the
> Oozie database, adding/removing columns and indexes, changing the default
> value of columns, etc. The issues caused by this can be very difficult to
> track down because their cause is not obvious and we generally assume the
> database schema is correct. For example, we saw an issue where Oozie was
> taking a long time to create Coordinator actions, and it turned out that the
> cause was that some indexes were missing, which made the Purge queries slow,
> which slowed down the whole database whenever the PurgeService ran. Another
> example was that the pause time was automatically being set whenever a
> Coordinator job was submitted, because the default value for the column was
> incorrect.
> We should create a Service which periodically runs and checks that the schema
> is correct. It can output details about what's wrong to the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
