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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/11/13 12:34:18 UTC

[jira] [Resolved] (OAK-496) More specific error reporting for Microkernel.commit

     [ https://issues.apache.org/jira/browse/OAK-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-496.
----------------------------------

    Resolution: Won't Fix

Resolving as WONTFIX for now. This issue blocked OAK-442, which was resolved otherwise.

If we still need more specific error reporting later we can re-open this issue again.

> More specific error reporting for Microkernel.commit
> ----------------------------------------------------
>
>                 Key: OAK-496
>                 URL: https://issues.apache.org/jira/browse/OAK-496
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mk, mongomk
>            Reporter: Michael Dürig
>
> Currently there is no way for upper layers to tell why a call to {{Microkernel.commit}} failed. 
> In order to be able to re-try a failed commit, we'd need a way to determine whether a commit failed due to a merge problem or due to another problem. In the former case retrying makes sense while in the latter it doesn't. 
> See also OAK-442



--
This message was sent by Atlassian JIRA
(v6.1#6144)