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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/08/08 13:21:12 UTC

[jira] [Commented] (OAK-2020) NodeState view at given version is not stable with DocumentNodeStore

    [ https://issues.apache.org/jira/browse/OAK-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090652#comment-14090652 ] 

Chetan Mehrotra commented on OAK-2020:
--------------------------------------

Added a testcase in http://svn.apache.org/r1616719 to demonstrate the issue

> NodeState view at given version is not stable with DocumentNodeStore
> --------------------------------------------------------------------
>
>                 Key: OAK-2020
>                 URL: https://issues.apache.org/jira/browse/OAK-2020
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>            Reporter: Chetan Mehrotra
>             Fix For: 1.1
>
>
> DocumentNodeStore should provide same NodeState for given (path, revision)  whenever a NodeState is obtained from it. This fails in some cases if the Node cache in DocumentNodeStore gets overflown and then the NodeState returned differs. This causes issues like
> # Spurious Commits see - Some commit would fails with conflicts in paths which were not modified in that commit
> # Diff logic would traverse those paths which are not related to changes done in that commit
> More details would be provided in comments below



--
This message was sent by Atlassian JIRA
(v6.2#6252)