[
https://issues.apache.org/jira/browse/JCR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570054#comment-13570054
]
Sergiy Shyrkov commented on JCR-3507:
-------------------------------------
Hello,
we also would like to see the functionality of removing orphaned history (in
one operation) in the internal API.
Right now we have a utility that "scans" the version storage for orphaned
histories (for nodes, which are no longer present in the repository) and
removes the histories by removing versions one by one (removal of each version
takes approx. 200-300 ms, depending on the repository size).
And we also had an issue that we cannot remove the orphaned version history
which contains only rootVersion (see JCR-3238 ) so we had to adjust locally the
o.a.j.c.version.InternalVersionHistoryImpl.removeVersion(Name) to allow the
removal of rootVersion and the version history itself if the version history is
unreferenced (!vMgr.hasItemReferences(node.getNodeId())) and there is only
rootVersion left (childNodes.length == 2).
If there would be a single operation to delete the complete (orphaned) version
history this could significantly speed-up the cleanup.
Thank you in advance!
Kind regards
Sergiy Shyrkov
> Make it possible to remove version histories via the internal version
> management API
> ------------------------------------------------------------------------------------
>
> Key: JCR-3507
> URL: https://issues.apache.org/jira/browse/JCR-3507
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, versioning
> Reporter: Unico Hommes
> Assignee: Unico Hommes
> Fix For: 2.7
>
>
> Version histories can become orphaned. This happens when the subject node is
> removed from the repository. In order to deal with the problem of
> indefinitely growing data stores, it should be possible to create
> functionality that removes such orphaned version histories.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
