[SERVER-61462] Create mongoq-specific versions of dropCollection, renameCollection, and dropDatabase Created: 12/Nov/21 Updated: 06/Dec/22 Resolved: 06/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Sprint: | Server Serverless 2021-11-29 | ||||||||
| Participants: | |||||||||
| Description |
|
Mongos calls sharding-specific commands shardsvrDropCollection, shardsvrRenameCollection, shardsvrDropDatabase against the primary shard for the database. However, mongoq needs to be deployed in front of non-shardsvr replica sets, so cannot call these shardsvr commands. This ticket is to:
This ticket depends on |