[
https://issues.apache.org/jira/browse/OOZIE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555306#comment-14555306
]
Bowen Zhang edited comment on OOZIE-2245 at 5/21/15 11:52 PM:
--------------------------------------------------------------
[~rkanter], do you plan to make it into 4.2? I would want to check it in for
future release. If that's the case, do you need to come back to modify this
patch if we have a new Db schema for oozie-5.0? Looks like you have already
disabled the check if the DB is sqlserver. BTW, can you post it in Review Board?
was (Author: bowenzhangusa):
[~rkanter], do you plan to make it into 4.2? I would want to check it in for
future release. If that's the case, do you need to come back to modify this
patch if we have a new Db schema for oozie-5.0? BTW, can you post it in Review
Board?
> 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.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)
