[SERVER-67779] Refactor `deleteRangeInBatches` to don't require an executor Created: 05/Jul/22 Updated: 29/Oct/23 Resolved: 11/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25 |
| Participants: |
| Description |
|
The deleteRangeInBatches function is currently accepting as argument an executor and returning an ExecutorFuture. However, with the introduction of the range deleter service, the deletion will have to be called from within an executor. Purpose of this ticket is to pull out the current code in a function deleteRangeInBatches, make it accept an OperationContext* and make it public. This way it can both be called by the legacy range deleter (via a new function deleteRangeInBatchesWithExecutor) and by the new range deleter service. |
| Comments |
| Comment by Githook User [ 11/Jul/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |