Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-1550 Incorrect handling of addExistingNode conflict in NodeStore
  3. OAK-2673

Resolve add-add, delete-delete merge conflict for empty hidden docs

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.13, 1.2
    • Component/s: mongomk
    • Labels:
      None

      Description

      While OAK-1550 is about general fix for resolving same node merge conflicts. But until general issue is fixed, we should special case for hidden nodes (e.g. index sub-tree).
      Discussed offline with Marcel Reutegger and Chetan Mehrotra about handling merge conflict for hidden nodes. Main concern to not resolve the conflict seemed to be observation (specifying/declaring what events reach which clients). For hidden nodes, observation isn't a concern. Along with that, in heavy write scenarios there are some cases (I'm aware of property index updates) which often cause conflicts – thereby wasting some time during merge attempts.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              mreutegg Marcel Reutegger
              Reporter:
              catholicon Vikas Saurabh

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment