You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/09/29 16:16:04 UTC

[jira] [Commented] (OAK-3455) Improve conflict exception message

    [ https://issues.apache.org/jira/browse/OAK-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935226#comment-14935226 ] 

Julian Reschke commented on OAK-3455:
-------------------------------------

+1 on making the messages more helpful.

Other than that, does this distinction have any impact on what the caller can do? If the conflicting revision can be seen locally, refreshing the session and retrying the changes could succeed, right? In that case, can we do something so that the caller knows whether a rety is worth the effort?

> Improve conflict exception message
> ----------------------------------
>
>                 Key: OAK-3455
>                 URL: https://issues.apache.org/jira/browse/OAK-3455
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>
> The conflict exception message for the DocumentNodeStore could be improved by adding information about the visibility of the conflict revision.
> A conflict across cluster nodes is the most likely case and it would be good to know if the other revision is already visible to the current cluster node. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)