jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCRVLT-18) Set default autosave threshold based on repository implementation
Date Mon, 21 Oct 2013 10:12:42 GMT

    [ https://issues.apache.org/jira/browse/JCRVLT-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800521#comment-13800521

Thomas Mueller commented on JCRVLT-18:

[~fmeschbe] I understand.

> I would suggest to remove auto save alltogether and rather instruct users to use smaller

That would be best - fast and secure, even for CRX 2.x that doesn't support large transactions

> 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

View raw message