jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marek Slama (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-134) Unreferenced VersionHistory should be deleted automatically.
Date Wed, 15 Feb 2012 13:59:00 GMT

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

Marek Slama commented on JCR-134:

There is one use case where it fails: When I have versionable node but never create version
using VersionManager so there is only rootVersion. I assume VersionHistory removal is triggered
by removing last non root Version so it is understandable. To fix this it would be good to
have some way how to explicitly remove also rootVersion after versionable node remove so this
removal of rootVersion could trigger removal of version history. It would be good to allow
rootVersion removal when its versioned node is already removed. Does it make sense to create
issue for this use case?

(Yes it is our mistake as we set versionable node which was not actually used as versioned
node. We could workaround it by creating one additional regular version and then removing
node, this new version to do full version history cleanup.)
> Unreferenced VersionHistory should be deleted automatically.
> ------------------------------------------------------------
>                 Key: JCR-134
>                 URL: https://issues.apache.org/jira/browse/JCR-134
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: versioning
>            Reporter: Tobias Bocanegra
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.6
>         Attachments: jackrabbit-1.4.x-JCR-134-first-try-2008-08-11.patch
> since the creation of a VersionHistory is triggered by the creation of a mix:versionable
node, the removal should happen automatically, as soon as no references to that version histroy
exist anymore. this is the case, when all mix:versionable nodes (in all workspaces) belonging
to that VH are deleted, and all the versions in the VH are removed i.e. only the jcr:rootVersion
is left. At this point, the VH should be deleted aswell.

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