You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by artifex <ar...@kiberry.ru> on 2005/02/22 06:30:53 UTC
lost nodes after delete()?
Hi,
After creating huge amount nodes in repository, calling checkIn/CheckOut for
some nodes and then removing content, it was found out, that remains
garbage(?) in file system.
I do approximately such sequence of actions:
1. after creating repository & certain base content
40 files / 49 folders in repository
2. creating a quantity of nodes
567 files / 457 folders in repository
3. CheckIn/CheckOut for some nodes + label additions
779 files / 614 folders in repository
4. Moving nodes
771 files/605 folders in repository
5. Removing all content (except nodes from point #1 )
212 files/191 folder in repository
212 not equal 40! For example, In \version\blobs\xx\xx\... folder I can
see files on which contents it is possible to define, that they should be
removed earlier.
Really a problem or I something incorrectly do it?
(Sorry for my english)
Thanks,
Vadim
Re: lost nodes after delete()?
Posted by Tobias Strasser <to...@gmail.com>.
> Whether correctly I have understood, what if I shall delete versions in
> VH(except rootVersion?), I shall reduce quantity of files if is not
> planned to come back to deleted nodes?
yes, you can also delete root version, once all references to it are deleted.
> Whether I can remove correctly VersionHistory as node?
no, this is not possible.
--
------------------------------------------< tobias.strasser@day.com >---
Tobias Strasser, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---
Re: lost nodes after delete()?
Posted by artifex <ar...@kiberry.ru>.
Hi Tobias,
Thanks for explanations.
Whether correctly I have understood, what if I shall delete versions in
VH(except rootVersion?), I shall reduce quantity of files if is not
planned to come back to deleted nodes?
Whether I can remove correctly VersionHistory as node?
Thanks,
Vadim
Tobias Strasser wrote:
>hi vadim,
>your obsevations are correct. this results out of 2 reasons:
>1) deleting a node does not delete its assosiated version history.
>that means, the versionhistory and all its versions will be kept for
>later restore. the VersionHistory.removeVersion() can remove versions.
>the history itself cannot be removed, and will stay in the repository
>for ever (jackrabbit will remove the VH when all its versions were
>removed).
>2) there is still a little bug in the versioning, that does not
>properly remove persistence data of removed versions and/or version
>labels. but this will be solved soon. i will create a jira issue for
>this: http://issues.apache.org/jira/browse/JCR-50
>
>cheers, tobi
>
>On Tue, 22 Feb 2005 08:30:53 +0300, artifex <ar...@kiberry.ru> wrote:
>
>
>>Hi,
>>
>>After creating huge amount nodes in repository, calling checkIn/CheckOut for
>>some nodes and then removing content, it was found out, that remains
>>garbage(?) in file system.
>>I do approximately such sequence of actions:
>>
>>1. after creating repository & certain base content
>>40 files / 49 folders in repository
>>2. creating a quantity of nodes
>>567 files / 457 folders in repository
>>3. CheckIn/CheckOut for some nodes + label additions
>>779 files / 614 folders in repository
>>4. Moving nodes
>>771 files/605 folders in repository
>>5. Removing all content (except nodes from point #1 )
>>212 files/191 folder in repository
>>
>>212 not equal 40! For example, In \version\blobs\xx\xx\... folder I can
>>see files on which contents it is possible to define, that they should be
>>removed earlier.
>>
>>Really a problem or I something incorrectly do it?
>>
>>(Sorry for my english)
>>
>>Thanks,
>>Vadim
>>
>>
>>
>>
>
>
>
>
Re: lost nodes after delete()?
Posted by Tobias Strasser <to...@gmail.com>.
hi vadim,
your obsevations are correct. this results out of 2 reasons:
1) deleting a node does not delete its assosiated version history.
that means, the versionhistory and all its versions will be kept for
later restore. the VersionHistory.removeVersion() can remove versions.
the history itself cannot be removed, and will stay in the repository
for ever (jackrabbit will remove the VH when all its versions were
removed).
2) there is still a little bug in the versioning, that does not
properly remove persistence data of removed versions and/or version
labels. but this will be solved soon. i will create a jira issue for
this: http://issues.apache.org/jira/browse/JCR-50
cheers, tobi
On Tue, 22 Feb 2005 08:30:53 +0300, artifex <ar...@kiberry.ru> wrote:
> Hi,
>
> After creating huge amount nodes in repository, calling checkIn/CheckOut for
> some nodes and then removing content, it was found out, that remains
> garbage(?) in file system.
> I do approximately such sequence of actions:
>
> 1. after creating repository & certain base content
> 40 files / 49 folders in repository
> 2. creating a quantity of nodes
> 567 files / 457 folders in repository
> 3. CheckIn/CheckOut for some nodes + label additions
> 779 files / 614 folders in repository
> 4. Moving nodes
> 771 files/605 folders in repository
> 5. Removing all content (except nodes from point #1 )
> 212 files/191 folder in repository
>
> 212 not equal 40! For example, In \version\blobs\xx\xx\... folder I can
> see files on which contents it is possible to define, that they should be
> removed earlier.
>
> Really a problem or I something incorrectly do it?
>
> (Sorry for my english)
>
> Thanks,
> Vadim
>
>
--
------------------------------------------< tobias.strasser@day.com >---
Tobias Strasser, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---