[
https://issues.apache.org/jira/browse/JCR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Hendriks updated JCR-2034:
----------------------------------
Attachment: JCR-2034.patch
Here's a possible solution that disables the schema checks if you specify the
java option org.apache.jackrabbit.core.util.db.schemacheck with value false. By
default the schema check is enabled.
> Add an option so skip the "checkSchema" methods
> -----------------------------------------------
>
> Key: JCR-2034
> URL: https://issues.apache.org/jira/browse/JCR-2034
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: config, jackrabbit-core
> Affects Versions: 1.5.3, core 1.4.9
> Reporter: Martijn Hendriks
> Priority: Minor
> Attachments: JCR-2034.patch
>
>
> Sometimes the "checkSchema" methods in the various components (DB filesystem,
> DB persistence manager, DB journal) fail to detect that the required tables
> already exist with as result that the startup fails. (See the mail thread on
> the dev list: http://jackrabbit.markmail.org/message/jtq2sqis2aceh7ro).
> An option to just skip the checkSchema methods on startup would solve this
> issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
