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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2017/07/18 08:14:00 UTC

[jira] [Resolved] (OAK-6455) Don't call observer concurrently from the CompositeNodeStore

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

Tomek Rękawek resolved OAK-6455.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.4

> Don't call observer concurrently from the CompositeNodeStore
> ------------------------------------------------------------
>
>                 Key: OAK-6455
>                 URL: https://issues.apache.org/jira/browse/OAK-6455
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: composite
>            Reporter: Tomek Rękawek
>             Fix For: 1.8, 1.7.4
>
>
> Per Observer interface
> {noformat}
> However, each observer is
>  * always guaranteed to see a linear sequence of changes. In other words the
>  * method will not be called concurrently from multiple threads and successive
>  * calls represent a linear sequence of repository states, i.e. the root
>  * state passed to a call is guaranteed to represent a repository state
> {noformat}
> Currently concurrent merge would result in concurrent calls to Observer. So that would need to be serialized



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)