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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2017/03/17 12:30:42 UTC
[jira] [Updated] (OAK-5944) VersionGarbageCollector: allow to
update _deletedOnce in batch operations
[ https://issues.apache.org/jira/browse/OAK-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated OAK-5944:
--------------------------------
Description:
Right now, we collect the update operations in batches, but then issue individual update operations.
A special-case API that takes a set of updates and applies them in a single DB operation might speed up things, in particular when there's a network hop.
Related to this, we may want to think about whether we need to attach a modified check to each single operation (by keeping the {{_modified}} value for each {{_id}}). Wouldn't it be sufficient to just check that the {{_modified}} value is not newer than the end of the time window for the VGC run?
> VersionGarbageCollector: allow to update _deletedOnce in batch operations
> -------------------------------------------------------------------------
>
> Key: OAK-5944
> URL: https://issues.apache.org/jira/browse/OAK-5944
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Julian Reschke
>
> Right now, we collect the update operations in batches, but then issue individual update operations.
> A special-case API that takes a set of updates and applies them in a single DB operation might speed up things, in particular when there's a network hop.
> Related to this, we may want to think about whether we need to attach a modified check to each single operation (by keeping the {{_modified}} value for each {{_id}}). Wouldn't it be sufficient to just check that the {{_modified}} value is not newer than the end of the time window for the VGC run?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)