[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: 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 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: |