You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/02 16:17:32 UTC

[jira] [Resolved] (JCR-2551) Recovery from a lost version history

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

Jukka Zitting resolved JCR-2551.
--------------------------------

    Resolution: Duplicate

Resolving as a duplicate of JCR-3101.
                
> Recovery from a lost version history
> ------------------------------------
>
>                 Key: JCR-2551
>                 URL: https://issues.apache.org/jira/browse/JCR-2551
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-core, versioning
>            Reporter: Jukka Zitting
>
> I'm working on a case where the entire version storage is lost and would like to add a recovery feature that can restore the repository to a consistent state after such an event. This feature should look for all versionable nodes in the repository and either remove all broken references to the version storage (making the node unversionable) or automatically reconnect the nodes to new empty version histories.

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