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

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

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

Vikas Saurabh edited comment on OAK-3474 at 10/15/16 3:21 PM:
--------------------------------------------------------------

Backported to 1.2 at [r1765072|https://svn.apache.org/r1765072] and to 1.0 at [r1765084|https://svn.apache.org/r1765084].


was (Author: catholicon):
Backported to 1.2 at [r1765072|https://svn.apache.org/r1765072].

> 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: core, mongomk
>            Reporter: Vikas Saurabh
>            Assignee: Marcel Reutegger
>              Labels: performance
>             Fix For: 1.4, 1.3.8, 1.0.35, 1.2.21
>
>
> {{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)