jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Boston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4529) DocumentNodeStore does not have a repository software version range check.
Date Mon, 04 Jul 2016 16:45:11 GMT

    [ https://issues.apache.org/jira/browse/OAK-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361577#comment-15361577

Ian Boston commented on OAK-4529:

The default behavior should be safe and do no damage, as a user of oak-run or other utilities
will not know they are about to corrupt the repository, and when they do, it will be too late.
ie safe by default. 
It should be possible to override the default behaviour to allow an upgrade to be performed.

> DocumentNodeStore does not have a repository software version range check.
> --------------------------------------------------------------------------
>                 Key: OAK-4529
>                 URL: https://issues.apache.org/jira/browse/OAK-4529
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.14, 1.0.31, 1.5.4, 1.4.4
>            Reporter: Ian Boston
> DocumentNodeStore does not currently check which software version the persisted repository
it is connecting to was created with or last updated. There is a risk that if the versions
are incompatible the repository may be damaged.
> Somewhere in the repository, the version of the software that created it, and the versions
that written to it should be stored. In the case of TarMK this information could be on local
disk near the TarMK files. In the case of a DocumentMK implementation, the information should
be stored in the "database" itself.
> When a DocumentNodeStore instance connects it should: check the versions stored in the
repository then check the versions are within a compatible range and refuse to start if not.
> When a DocumentNodeStore writes to a repository, it should add its version to the list
of versions that have updated the repository.
> This check behaviour should be active in full Oak or any utilities (eg oak-run).

This message was sent by Atlassian JIRA

View raw message