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

Incorrect handling of addExistingNode conflict in NodeStore

Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      MicroKernel.rebase says: "addExistingNode: node has been added that is different from a node of them same name that has been added to the trunk."

      However, the NodeStore implementation

      1. throws a CommitFailedException itself instead of annotating the conflict,
      2. also treats the equal childs with the same name as a conflict.

      Attachments

        Issue Links

        blocks

        Bug - A problem which impairs or prevents the functions of the product. OAK-1541 Concurrent creation of users chokes on intermediate paths

        • Major - Major loss of function.
        • Closed
        is blocked by

        Bug - A problem which impairs or prevents the functions of the product. OAK-1185 DocumentNodeStore: annotate conflicts

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mreutegg Marcel Reutegger
            mduerig Michael Dürig
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment