Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-50013

update with same value as existing key in ephemeralForTest radix store should be a no-op

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL

      Otherwise you can end up with different stores depending on how changes are merged in.

      Case 1:
      base.insert

      {a, a}
      other = base
      me = base
      other.update{a, b}
      merge other to master = {a, b}
      me.update{a, a}

      merge me to master =

      {a, b}

      Case 2:
      base.insert{a, a}
      other = base
      other.update{a, b}

      merge other to master =

      {a, b}

      me = other
      me.update

      {a, a}
      merge me to master = {a, a}

      If the order is Case 1, update need to fail so we know there is nothing to merge in

            Assignee:
            henrik.edin@mongodb.com Henrik Edin
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: