[
https://issues.apache.org/jira/browse/JCRVLT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800817#comment-13800817
]
Tobias Bocanegra commented on JCRVLT-18:
----------------------------------------
> I would suggest to remove auto save alltogether and rather instruct users to
> use smaller packages.
which is not very practical. the system should be able to create and restore
packages with unlimited # of nodes and content size. it should be smart enough
to distinguish between "system content" that contains bundles, configuration,
scripts, etc, that need to be "saved" atomatically. And between "user content"
that should be imported best effort. worst experience would be that an import
that takes several hours fails at the end, because of a
ConcurrentModificationException.
> Set default autosave threshold based on repository implementation
> -----------------------------------------------------------------
>
> Key: JCRVLT-18
> URL: https://issues.apache.org/jira/browse/JCRVLT-18
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Tobias Bocanegra
> Priority: Minor
>
> with jackrabbit 2.0 we had a limitation of the size of the transient space as
> it is held in memory. in order to support large packages, the AutoSave
> threshold is set to 1024 nodes.
> with jackrabbit 3.0 the transient space is more or less unlimited in size,
> and we can install large packages in 1 save, which improves installation
> atomicity.
> however, the bigger the transient size, the higher the chance for collisions
> during installation of large packages, so saving in chunks yields to a more
> robust installation behavior.
> suggestions:
> - autosave threshold of 0 should mean 'auto'
> - autosave threshold of -1 should mean 'never'
> - packages can provide their desired autosave threshold via properties
--
This message was sent by Atlassian JIRA
(v6.1#6144)
