[
https://issues.apache.org/jira/browse/OAK-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924133#comment-16924133
]
Stefan Egli commented on OAK-8591:
----------------------------------
The core fix ({{doc.isVisible -> isVisible}}) makes sense. What I was wondering
if there's any implication of the fix elsewhere. Eg {{isValidRevision}} also
gets used by {{getLatestValue}} which in turn is used by {{getNodeAtRevision}}:
I'm wondering if this fix also changes (fixes) the behaviour of
{{getNodeAtRevision}} ?
> Conflict exception on commit
> ----------------------------
>
> Key: OAK-8591
> URL: https://issues.apache.org/jira/browse/OAK-8591
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Critical
>
> Under some conditions it may happen that a commit to the DocumentStore fails
> with a ConflictException even though there is no conflicting change. This
> includes regular commits as well as branch commits.
> The actual problem is with NodeDocument.getNewestRevision(). This method is
> used in Commit.checkConflicts() to find out when the most recent change
> happened on a node and find conflicts. The returned value is incorrect and
> may e.g. return null even though the node exists. This will then trigger the
> ConflictException.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
