[
https://issues.apache.org/jira/browse/OAK-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010457#comment-15010457
]
Marcel Reutegger commented on OAK-3634:
---------------------------------------
For consistency with behavior of other write operations in the DocumentStore, I
would still suggest to fix/change update(). All other write operations make
changes visible that happened before. This is a requirement for conflict
detection. So far the conflict detection does not depend on update(), which
probably means there is no urgent need to change the current implementation. A
commit either uses create(), createOrUpdate() or findAndUpdate(). Those
operations ensure the happens before semantics.
> 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)
