jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3115) Versioning fixup leaves persistence in a state where the node can't be made versionable again
Date Mon, 17 Oct 2011 15:00:12 GMT

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

Julian Reschke commented on JCR-3115:

r1185228: added test case for breaking and fixing version storage (also add hook for running
consistency check in "fix" mode)

So at least some types of broken versioning PM can be fixed by the bundle consistency check
sufficiently to reenable versioning.
> Versioning fixup leaves persistence in a state where the node can't be made versionable
> ---------------------------------------------------------------------------------------------
>                 Key: JCR-3115
>                 URL: https://issues.apache.org/jira/browse/JCR-3115
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, versioning
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>         Attachments: AutoFixCorruptNode.java
> Jackrabbit's version recovery mode (org.apache.jackrabbit.version.recovery system property)
disconnects all version histories that expose problems that manifest in unexpected exceptions
being thrown. "disconnects" means removing the properties defined for mix:versionable and
removing the mixin type. The actual versioning related nodes remain in place.
> The problem: when re-adding mix:versionable, ItemSaveOperation.initVersionHistories tries
to create the new version history in the same location (the path being derived from the versionable
node's identifier), and consequently fails because of the broken underlying storage.
> (attaching a work-in-progress test case that illustrates the problem)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message