Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-496

More specific error reporting for Microkernel.commit

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • mk, mongomk
    • None

    Description

      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

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. OAK-442 Concurrently adding nodes fails with CommitFailedException

          • Major - Major loss of function.
          • Closed
          incorporates

          Bug - A problem which impairs or prevents the functions of the product. OAK-507 MicroKernel.commit() throws NotFoundException for an existing node

          • Major - Major loss of function.
          • Closed
          is part of

          Improvement - An improvement or enhancement to an existing feature or task. OAK-11 Document and tighten contract of Microkernel API

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              mduerig Michael Dürig
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: