[DRIVERS-1854] Efficient Multi-deletes Created: 15/Jul/21 Updated: 31/May/22 Resolved: 20/Dec/21 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Driver Changes: | Needed | ||||
| Server Compat: | 6.0, 6.1 | ||||
| Upstream Changes Summary: | PM-2227 exposes a new BATCHED_DELETE query execution stage for efficiently deleting large ranges of data in batches. This stage is a more performant alternative to the classic DELETE stage and is available for internal operations, and enabled by default for user-initiated multi:true deletions. |
||||
| Description |
|
Downstream Change Summary This will have a new oplog entry, so we expect a lot of downstream impacts. Description of Linked TicketEpic Summary SummaryAllow the truncate command, developed by PM-2375, to efficiently range-delete clustered collections that have secondary indexes. MotivationThe truncate operation will allow more efficient TTL deletes of time-series buckets, and it will allow Serverless clustered collections to efficiently delete data over arbitrary ranges. Cast of Characters
Documentation |
| Comments |
| Comment by PM Bot [ 13/Jan/22 ] |
|
If you are not logged in, you can view the tickets in this epic by following this link. |
| Comment by PM Bot [ 20/Dec/21 ] |
|
Moved to Needs Triage because a linked PM issue (PM-2227)was moved to Ready for Work. |
| Comment by Esha Bhargava [ 18/Oct/21 ] |
|
No driver changes needed. |
| Comment by PM Bot [ 12/Oct/21 ] |
|
Moved to Needs Triage because a linked PM issue (PM-2227)was moved to Ready for Work. |
| Comment by PM Bot [ 20/Aug/21 ] |
|
Moved to Needs Triage because a linked PM issue (PM-2227)was moved to Ready for Work. |
| Comment by Alexander Golin (Inactive) [ 26/Jul/21 ] |
|
Triage: may need driver changes, depends on if these changes show up in change streams - blocking on PM-2227 so we can reevaluate once that is further scoped. |