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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2015/10/05 15:13:26 UTC

[jira] [Created] (OAK-3474) NodeDocument.getNodeAtRevision can go into property history traversal when latest rev on current doc isn't committed

Vikas Saurabh created OAK-3474:
----------------------------------

             Summary: NodeDocument.getNodeAtRevision can go into property history traversal when latest rev on current doc isn't committed
                 Key: OAK-3474
                 URL: https://issues.apache.org/jira/browse/OAK-3474
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: mongomk
            Reporter: Vikas Saurabh


{{NodeDocument.getNodeAtRevision}} tried to look at latest revisions entries for each property in current document. But it just looks at the *last* entry for a given property. In case this last entry isn't committed, the code would go into previous documents to look for a committed value.

(cc [~mreutegg])



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)