You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Robin Brouns (Jira)" <ji...@apache.org> on 2020/09/07 14:18:00 UTC
[jira] [Commented] (OAK-8048) VersionHistory not removed when
removing node and all its versions
[ https://issues.apache.org/jira/browse/OAK-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191727#comment-17191727 ]
Robin Brouns commented on OAK-8048:
-----------------------------------
We're facing the exact same issue. I've got a lot of _nt:versionHistory_ nodes in our repository without any version except the _jcr:rootVersion_. There are no valid references anymore for the _jcr:versionableUuid_. Until now I haven't found a way to delete them, except by migrating the repository with oak-upgrade (without copying version info). Is there any progress in getting a fix for this issue because it will lead to a lot of unused _nt:versionHistory_ nodes in our repository?
> 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)