[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated OAK-2066: -- Component/s: rdbmk documentmk core > 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: core, documentmk, mongomk, rdbmk >Reporter: Julian Reschke >Assignee: Marcel Reutegger >Priority: Blocker > Labels: performance > Fix For: 1.3.15 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Michael Marth updated OAK-2066: --- Priority: Blocker (was: Major) > 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 >Priority: Blocker > Labels: performance > Fix For: 1.4, 1.3.15 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Michael Marth updated OAK-2066: --- Fix Version/s: 1.3.15 > 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.4, 1.3.15 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Tomek Rękawek updated OAK-2066: --- Fix Version/s: 1.4 > 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.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)
[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated OAK-2066: -- Fix Version/s: (was: 1.3.9) > 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 > > 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)
[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated OAK-2066: -- Fix Version/s: (was: 1.3.7) 1.3.8 > 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.8 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Amit Jain updated OAK-2066: --- Fix Version/s: (was: 1.3.6) 1.3.7 > 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.7 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Amit Jain updated OAK-2066: --- Fix Version/s: (was: 1.3.7) 1.3.6 > 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.6 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Michael Marth updated OAK-2066: --- Fix Version/s: (was: 1.3.5) 1.3.7 > 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.7 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Davide Giannella updated OAK-2066: -- Fix Version/s: (was: 1.3.4) 1.3.5 > 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.5 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated OAK-2066: -- Labels: performance (was: ) > 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)
[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated OAK-2066: -- Fix Version/s: 1.3.4 > 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)
