[SERVER-70544] Multideletes with a single document should not be applyOps entries Created: 13/Oct/22 Updated: 29/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Shin Yee Tan | Assignee: | Shin Yee Tan |
| 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: | Execution Team 2022-10-31, Execution Team 2022-11-14 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When multi-deletes are enabled, for example with TTL indexes, and we identify a single document to delete, we wrap the operation in an applyOps oplog entry. We should keep the oplog entry as 1 operation without making it an applyOps. |
| Comments |
| Comment by Githook User [ 01/Nov/22 ] |
|
Author: {'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}Message: |