[OAK-7401] Changes kept in memory when update limit is hit in commit hook

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.2, 1.4, 1.6.0, 1.8.0
• Fix Version/s: 1.9.0, 1.10.0
• Component/s: documentmk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 11/Apr/18 06:30
• Updated: 10/May/23 10:49
• Resolved: 23/Apr/18 07:42

Description

In some cases no persisted branch is created by the DocumentNodeStore when the number of changes hit the update limit. This happens when the current branch state is in-memory and the commit hook contributes changes that reach the update limit. The implementation keeps those changes in memory, which may lead to a commit way bigger than specified by the update limit.

Issue Links

• causes: OAK-8691 Incorrect base state from node builder
• is related to: OAK-7801 CompositeNodeStore.merge() may trigger conflicting branches