[
https://issues.apache.org/jira/browse/JCR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567568#comment-13567568
]
Unico Hommes commented on JCR-3507:
-----------------------------------
Do you mean that we add a configuration option to check against whether such
actions are allowed or not before proceeding with the remove? Note that the
internal API already has the ability to remove individual versions of the
version histories, just not the entire version history object. If we add such a
check I propose we also use it to check whether removing individual versions is
allowed.
> 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
> 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
