[jira] Created: (JCR-2034) Add an option so skip the "checkSchema" methods

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: core 1.4.9, 1.5.3
            Reporter: Martijn Hendriks
            Priority: Minor


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.

     [ 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.

     [ https://issues.apache.org/jira/browse/JCR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2034:
-------------------------------

    Status: Patch Available  (was: Open)

> 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: core 1.4.9, 1.5.3
>            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.

    [ https://issues.apache.org/jira/browse/JCR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728720#action_12728720 ]

Jukka Zitting commented on JCR-2034:
------------------------------------

Could this be a normal Jackrabbit configuration option instead of a system property?

> 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.

    [ https://issues.apache.org/jira/browse/JCR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729148#action_12729148 ]

Martijn Hendriks commented on JCR-2034:
---------------------------------------

Yes, on second thought I think that a normal configuration option is better. I'll create a new patch.

> 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.

     [ 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-v2.patch

...and here it is.

> 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-v2.patch, 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.

     [ https://issues.apache.org/jira/browse/JCR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Hendriks updated JCR-2034:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
           Status: Resolved  (was: Patch Available)

Committed revision 796957.

> 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
>             Fix For: 2.0.0
>
>         Attachments: JCR-2034-v2.patch, 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.

     [ https://issues.apache.org/jira/browse/JCR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2034:
-------------------------------

    Fix Version/s:     (was: 2.0.0)
                   1.6.0

Merged to the 1.x branch in revision 801133.

> 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
>             Fix For: 1.6.0
>
>         Attachments: JCR-2034-v2.patch, 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.