[
https://issues.apache.org/jira/browse/OAK-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010693#comment-15010693
]
Julian Reschke commented on OAK-3634:
-------------------------------------
So how do we proceed from here?
1) The aforementioned unit test checks something we intend to change (and I'm
guilty of writing that test). Should we fix/remove the test?
2) My concern is that allowing update() to populate the cache with potentially
incorrect information will make it harder to debug other caching related
issues, thus I'd propose to fix it right away.
> 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.3.10
> Reporter: Julian Reschke
> Attachments: OAK-3634.diff
>
>
> 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)
