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 "Marco Piovesana (Jira)" <ji...@apache.org> on 2020/02/18 07:16: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=17038840#comment-17038840 ] 

Marco Piovesana commented on OAK-8048:
--------------------------------------

Hi guys,
I know you might all very busy, but it's been a while since I've submitted the patch and I was wondering if it was going to be considered for any of the future releases. I have use cases where users create big versioned files that are useful only for a specific amount of time. Those files are deleted, but because of this bug, their base version remains there filling up the disk with unnecessary information.

> 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
>            Priority: Major
>         Attachments: OAK-8048-test.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)