[SERVER-52895] Handle captrunc and emptycapped during tenant migrations Created: 16/Nov/20 Updated: 14/Dec/22 Resolved: 17/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm-1791_other_required | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
captrunc truncates documents from a capped collection. It is a testing-only command that does no auth checks and doesn't generate oplog entries. emptycapped deletes all documents from a capped collection. It is a testing-only command that does no auth checks, though it does generate oplog entries. Since these are testing-only commands, I don't think we need to support them in serverless. Note that patch set 1 of this CR forĀ |
| Comments |
| Comment by Githook User [ 14/Dec/22 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: There are two TODO's on However, The TODO for captrunc was probably meant to be on The TODO for compact was probably meant to be on |