Ok, created a separate OAK-3018 for adapting backgroundWrite to use the
batch-update (once available)
Cheers,
Stefan
On 6/22/15 10:05 AM, Marcel Reutegger mreut...@adobe.com wrote:
Hi,
this is currently not possible because the DocumentStore API
does not have such a method. There's an existing issue closely
related to your request:
https://issues.apache.org/jira/browse/OAK-2066
I think in general it makes sense to add such a method. As
you can see in the issue, the background write is not the only
application that would benefit from it.
Regards
Marcel
On 18/06/15 17:24, Stefan Egli wrote:
Hi,
This might have been discussed before but just so I understand:
The DocumentNodeStore.backgroundWrite goes through the heavy work of
updating the lastRev for all pending changes and does so in a
hierarchical-depth-first manner. Unfortunately, if the pending changes
all
come from separate commits (as does not sound so unlikely), the updates
are
sent in individual update calls to mongo (whenever the lastRev differs).
Which, if there are many changes, results in many calls to mongo.
What about replacing that mechanism using mongo's bulk functionality (eg
initializeOrderedBulkOperation)? Is this for some reason not possible or
already in the jira-queue (which ticket)?
Cheers,
Stefan
--
http://api.mongodb.org/java/current/com/mongodb/DBCollection.html#initial
i
ze
OrderedBulkOperation--
