[
https://issues.apache.org/jira/browse/JCR-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782369#action_12782369
]
Julien Poffet commented on JCR-2407:
------------------------------------
According to the comment of Stefan, I think that it would be nice if we can
have an option to say if we want to read the blobs on demand. In my situation I
do not really care about performance. I'm just making a full scan of a
repository through WebDav to read the content and re-import it to a new
repository. My source repository is about 60go so I don't want 60go of blobs
cached in the temporary directory... As it is now, all the blobs are spooled to
the local file systems but deleted only when I stop tomcat. I tried to tuned
the cache manager with no better result...
> Make the disk space used by cached binary properties configurable
> -----------------------------------------------------------------
>
> Key: JCR-2407
> URL: https://issues.apache.org/jira/browse/JCR-2407
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Affects Versions: 2.0-beta1
> Reporter: Martijn Hendriks
> Attachments: repository.xml, workspace.xml
>
>
> Binary properties which are in Jackrabbit's caches (SharedItemStateManager
> eg) are stored on disk in the temp dir. This can cause problems on small
> temporary file systems as the size of the binary properties on disk is not
> limited by Jackrabbit. There is one way to influence this indirectly: make
> the Jackrabbit cache sizes smaller (via the CacheManager). It could be
> helpful in some cases if an upper bound on the disk usage can be given.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
