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 2016/10/15 14:15:20 UTC

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

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

Vikas Saurabh updated OAK-3474:
-------------------------------
    Fix Version/s: 1.2.21

> 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: candidate_oak_1_0, performance
>             Fix For: 1.4, 1.3.8, 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)