[SERVER-32365] Move the logic of the dropDatabase command into the new _configsvrDropDatabase command Created: 15/Dec/17  Updated: 30/Oct/23  Resolved: 16/Jan/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.7.2

Type: Task Priority: Major - P3
Reporter: Kaitlin Mahar Assignee: Kaitlin Mahar
Resolution: Fixed Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-12023 Docs for SERVER-32365: Move the logic... Closed
Related
is related to SERVER-36317 Mongos returns true when attempting t... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-01-01, Sharding 2018-01-15, Sharding 2018-01-29
Participants:

 Description   

The code currently in mongos's dropDatabase command should be moved into the new _configsvrDropDatabase command (created under SERVER-32363).
Mongos should now forward "dropDatabase" to the config server by sending _configsvrDropDatabase.



 Comments   
Comment by Gregory McKeon (Inactive) [ 27/Aug/18 ]

kay.kim this ticket changed the return value of the dropDatabase command when the database does not exist to ok: 1 when run against a mongos. It still results in an error ns not found when run against a replicaset or standalone mongod. Commenting here in case we want to document this change.

Comment by Githook User [ 16/Jan/18 ]

Author:

{'email': 'kaitlin.mahar@mongodb.com', 'name': 'Kaitlin Mahar', 'username': 'kmahar'}

Message: SERVER-32365 Move the logic of the dropDatabase command into the new _configsvrDropDatabase command
Branch: master
https://github.com/mongodb/mongo/commit/0bb9226dcedc4bcb98ce97f10f1262da3905d71b

Generated at Thu Feb 08 04:30:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.