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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.35, 1.2.21, 1.3.8, 1.4
• Component/s: core, mongomk
• Labels: performance
• Assignee: Marcel Reutegger
• Reporter: Vikas Saurabh
• Created: 05/Oct/15 13:12
• Updated: 15/Oct/16 15:21
• Resolved: 07/Oct/15 10:08

Description

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)