[SERVER-66210] BatchedDeleteStage doesn't indicate when completion is caused by pass targets Created: 04/May/22 Updated: 29/Oct/23 Resolved: 09/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2227-M3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2022-05-16 | ||||||||
| Participants: | |||||||||
| Description |
|
A BatchedDeleteStage can return PlanStage::IS_EOF in two different scenarios For batched deletes that specify pass targets, such as the TTLMonitor, it is useful to differentiate between the two scenarios to know if the command should be executed again |
| Comments |
| Comment by Githook User [ 09/May/22 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |