[SERVER-75798] Use LastOpFixer for update and delete operations in bulkWrite command Created: 06/Apr/23 Updated: 29/Oct/23 Resolved: 17/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaitlin Mahar | Assignee: | Kaitlin Mahar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2023-04-17, Repl 2023-05-01 |
| Participants: |
| Description |
|
Currently, we are only using the LastOpFixer for inserts run via bulkWrite. However, we need to use it for updates and deletes too, i.e. we should be calling startingOp() and finishedOpSuccessfully() before/after each update and delete. That way, if such an operation ends up being a no-op, we will still correctly wait for write concern after it. |
| Comments |
| Comment by Githook User [ 14/Apr/23 ] |
|
Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}Message: |