You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2023/04/18 09:31:00 UTC

[jira] [Resolved] (JCRVLT-697) Moving child nodes around should be calculated towards the autosave threshold

     [ https://issues.apache.org/jira/browse/JCRVLT-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke resolved JCRVLT-697.
-----------------------------------
    Resolution: Fixed

> Moving child nodes around should be calculated towards the autosave threshold
> -----------------------------------------------------------------------------
>
>                 Key: JCRVLT-697
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-697
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: vlt
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Major
>             Fix For: 3.6.10
>
>
> When overwriting nodes using sysview import, filevault moves child nodes and properties temporarily under temporary nodes. Depending on the number of child nodes, this may affect the size of changes in transient space, and is currently not considered when deciding when to save a snapshot.
> Proposal: when doing node stashing, the # of child nodes moved around should be added to the number of operations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)