[SERVER-50013] update with same value as existing key in ephemeralForTest radix store should be a no-op Created: 29/Jul/20  Updated: 29/Oct/23  Resolved: 30/Jul/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Henrik Edin Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

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



 Comments   
Comment by Githook User [ 30/Jul/20 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-50013 Update with same value as existing node in ephemeralForTest radix store should be a no-op
Branch: master
https://github.com/mongodb/mongo/commit/b223aaec1fa05c534855f9502ac02504c299874b

Generated at Thu Feb 08 05:21:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.