You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/06/22 10:32:00 UTC
[jira] [Commented] (OAK-2066) DocumentStore API: batch create, but
no batch update
[ https://issues.apache.org/jira/browse/OAK-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595502#comment-14595502 ]
Stefan Egli commented on OAK-2066:
----------------------------------
As mentioned [on the list|http://markmail.org/thread/mkrvhkfabit4osli] having a batch update could also speed up the {{DocumentNodeStore.backgroundWrite}} considerably - as currently backgroundWrite has to do one {{DocumentStore.update}} call per commit - while as this could otherwise be batched into (much) larger chunks.
> DocumentStore API: batch create, but no batch update
> ----------------------------------------------------
>
> Key: OAK-2066
> URL: https://issues.apache.org/jira/browse/OAK-2066
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Reporter: Julian Reschke
> Labels: performance
> Fix For: 1.3.4
>
>
> The DocumentStore API currently has a call for creating many nodes at once.
> However, this will sometimes fail for large save operations in JCR, because in the DS persistence, JCR-deleted nodes are still present (with a deleted flag). This causes two subsequent sequences of
> 1) create test container
> 2) create many child nodes
> 3) remove test container
> to behave very differently, depending on whether the test container is created for the first time or not.
> (see CreateManyChildNodesTest)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)