[
https://issues.apache.org/jira/browse/JCR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567598#comment-13567598
]
angela commented on JCR-3507:
-----------------------------
that makes sense.... the ability to remove versions is there because it's part
of the JCR API and nobody really
cared about the implications.
another question that is related to the security issue we are currently having
with the version store: how would
permissions be enforced on the internal remove versionhistory API? there is not
way place specific access
control for individual version histories... (see also JCR-2963 and JCR-3492).
> 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
