[OAK-2066] DocumentStore API: batch create, but no batch update

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.3.15, 1.4
• Component/s: core, documentmk, mongomk, rdbmk
• Labels: performance
• Epic Link: Improve DocumentMK performance
• Assignee: Marcel Reutegger
• Reporter: Julian Reschke
• Created: 01/Sep/14 15:04
• Updated: 02/Mar/16 15:22
• Resolved: 01/Feb/16 21:20

Description

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)

Issue Links

• blocks: OAK-3018 Use batch-update in backgroundWrite
• relates to: OAK-3748 Heuristic method to decide if the document may be a part of the bulk update

Sub-Tasks

• Bulk document updates in MongoDocumentStore: Closed
• ConflictException and CommitQueue should support a list of revisions: Closed
• Bulk document updates in RDBDocumentStore: Closed
• Add bulk createOrUpdate method to the DocumentStore API: Closed
• Use the bulk createOrUpdate in Commit: Closed
• Allow to acquire multiple locks: Closed
• Batch createOrUpdate() may fail with primary key violation: Closed
• Occasional failure in MultiDocumentStoreTest.batchUpdateCachedDocument(): Closed