[SERVER-59768] Drop collection return value is not honored in sharded clusters Created: 03/Sep/21 Updated: 15/Sep/23 Resolved: 15/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.1.0, 5.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Matt Panton |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18 | ||||
| Participants: | |||||
| Description |
|
The documentation specifies that a dropCollection command should return false if the collection to drop does not exist, but this behavior is not honored in sharded clusters using v5.0+ binaries. |
| Comments |
| Comment by Kaloian Manassiev [ 30/Jun/22 ] |
|
garaudy.etienne@mongodb.com to file a docs ticket to remove the references. |