[
https://issues.apache.org/jira/browse/OAK-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389877#comment-17389877
]
Marcel Reutegger commented on OAK-8048:
---------------------------------------
bq. do you mean to create a new node, add the mix:versionable mixin and set its
jcr:versionHistory property to reference the orphaned version history? Save
that. Aand then delete the newly created node again to trigger the
OrphanedVersionCleaner?
[~jsedding] Yes, that's what I had in mind. Though, you won't be able to set
the {{jcr:versionHistory}} property. It is protected and it is also not
necessary. The implementation will automatically link the versionable node with
the version history when the UUID of the versionable node matches the
{{jcr:versionableUuid}} on the version history.
> VersionHistory not removed when removing node and all its versions
> ------------------------------------------------------------------
>
> Key: OAK-8048
> URL: https://issues.apache.org/jira/browse/OAK-8048
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 1.8.9
> Reporter: Marco Piovesana
> Assignee: Manfred Baedke
> Priority: Major
> Attachments: OAK-8048-test.diff, OAK-8048.diff, fix-OAK-8048.patch
>
>
> Hi all,
> I'm trying to delete a node and all its versions, but the version history is
> not removed. I'm doing the following steps (as described in OAK-4370 and
> JCR-134):
> # retrieve the version history
> # delete the node and save the session
> # delete all versions except for the base version
> # save the session
> The versions are all gone but the versionHistory node, and the base version
> node, are still there. Am I doing something wrong?
> The only test related to this that I found is
> {{ReadOnlyVersionManagerTest.testRemoveEmptyHistoryAfterRemovingVersionable}}.
> It does work, but uses Oak related classes and not the JCR interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
