[SERVER-43043] Add idempotency test for two fields updates Created: 26/Aug/19 Updated: 29/Oct/23 Resolved: 30/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2019-09-09 | ||||||||
| Participants: | |||||||||
| Description |
|
Multi-field update op may fail because one field updates a subdocument or subarray field and the sub document/array doesn't exist (because it was deleted by a later op). In that case, the entire update failed to apply. Here's a concrete example.
|
| Comments |
| Comment by Githook User [ 31/Aug/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |
| Comment by Githook User [ 30/Aug/19 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}Message: |
| Comment by Siyuan Zhou [ 26/Aug/19 ] |
|
We also need to test applyOps to reflect MongoMirror's behavior. |