[ https://issues.apache.org/jira/browse/OAK-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268181#comment-15268181 ]
Marcel Reutegger commented on OAK-4321: --------------------------------------- You can probably get the system into this state when you modify data directly on the DocumentStore API level. E.g. shoot a hole into the hierarchy by removing a document with children than still exist. > Improve conflict exception message to show if conflict is unexpected > -------------------------------------------------------------------- > > Key: OAK-4321 > URL: https://issues.apache.org/jira/browse/OAK-4321 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core, documentmk > Reporter: Vikas Saurabh > Assignee: Vikas Saurabh > Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4 > Fix For: 1.6 > > Attachments: OAK-4321-1.0.diff > > > Merge exception (aka OakMergeXXXX) are often expected when concurrent > sessions do conflicting writes. But in some occasions, we've seen bugs in oak > which also lead to merge exception. > This creates confusion during investigation to isolate if it's an issue in > oak or a genuine concurrent conflict. > It'd be useful if the exception message has information to distinguish that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)