[
https://issues.apache.org/jira/browse/OAK-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142514#comment-15142514
]
Julian Reschke edited comment on OAK-3634 at 2/11/16 10:24 AM:
---------------------------------------------------------------
Yes, that's why it's labeled as 1.0 candidate :-). If the actual change did
apply without conflicts, I'd go ahead with the change right now, but they do
not, so this needs a bit of tuning the individual changes...
was (Author: reschke):
Yes, that's why it's labeled as 1.0 candidate :-). If the actual change did
apply without conflicts, I'd go ahead with the change for the 1.0.28. (Does it?)
> RDB/MongoDocumentStore may return stale documents
> -------------------------------------------------
>
> Key: OAK-3634
> URL: https://issues.apache.org/jira/browse/OAK-3634
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk, rdbmk
> Affects Versions: 1.2.7, 1.3.10, 1.0.23
> Reporter: Julian Reschke
> Assignee: Marcel Reutegger
> Labels: candidate_oak_1_0
> Fix For: 1.3.14, 1.2.11
>
> Attachments: OAK-3634.diff, OAK-3634.diff, OAK-3634.patch
>
>
> It appears that the implementations of the {{update}} method sometimes
> populate the memory cache with documents that do not reflect any current or
> previous state in the persistence (that is, miss changes made by another
> node).
> (will attach test)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
