[jira] [Updated] (OAK-1648) Creating multiple checkpoint on same head revision overwrites previous entries

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated OAK-1648:
----------------------------------
    Fix Version/s:     (was: 1.2)
                   1.3.0

Moved to 1.3 because this is only a minor issue and we currently only have a single client for the checkpoint functionality. The async index update always created a checkpoint with a fixed time-to-live.

An optimistic update in a cluster is still possible, even without the _modCount. The update would simply include a check on the expiryTime.

> Creating multiple checkpoint on same head revision overwrites previous entries
> ------------------------------------------------------------------------------
>
>                 Key: OAK-1648
>                 URL: https://issues.apache.org/jira/browse/OAK-1648
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> Currently when a checkpoint is created in DocumentNodeStore then it is saved in form of currentHeadRev=>expiryTime. Now if multiple checkpoints are created where head revision has not changed then only the last one would be saved and previous entries would be overridden as revision is used as key
> One fix would be to change the expiry time only if the new expiry time is greater than previous entry. However doing that safely in a cluster (check then save) is currently not possible with DocumentStore API as the modCount check if only supported for Nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)