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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2014/06/11 08:58:01 UTC

[jira] [Updated] (OAK-1822) NodeDocument _modified may go back in time

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

Marcel Reutegger updated OAK-1822:
----------------------------------

    Fix Version/s: 1.0.1

Yes, definitively makes sense. Added 1.0.1 fix version.

> NodeDocument _modified may go back in time
> ------------------------------------------
>
>                 Key: OAK-1822
>                 URL: https://issues.apache.org/jira/browse/OAK-1822
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 1.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>             Fix For: 1.0.1, 1.1
>
>
> In a cluster with multiple DocumentMK instances the _modified field of a NodeDocument may go back in time. This will result in incorrect diff calculations when the DocumentNodeStore uses the _modified field to find changed nodes for a given revision range.



--
This message was sent by Atlassian JIRA
(v6.2#6252)