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 14:01:08 UTC
[jira] [Resolved] (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 resolved OAK-1822.
-----------------------------------
Resolution: Fixed
Merged revisions 1594835,1594888,1601838 from trunk to 1.0 branch: http://svn.apache.org/r1601865
> 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)