[
https://issues.apache.org/jira/browse/OAK-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944587#comment-14944587
]
Marcel Reutegger commented on OAK-3474:
---------------------------------------
Thanks Vikas for reporting this issue. As discussed with you offline this may
lead to a severe performance issue when this happens on document with many
changes. That is, the root document is most vulnerable to this issue.
> 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.3.8
>
>
> {{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)
