[DOCS-14296] Investigate changes in SERVER-55145: Make dropping a nonexistent database a noop Created: 16/Mar/21  Updated: 17/Mar/21  Resolved: 17/Mar/21

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-55145 Make dropping a nonexistent database ... Closed
Participants:
Days since reply: 2 years, 47 weeks ago

 Description   

Description

Downstream Change Summary

This commit changed the response of a dropDatabase command.

In particular I've removed the following two optional fields from the response:

  • dopped
  • info

https://github.com/mongodb/mongo/commit/b134809bd5db091c0517ee0fb4378ad420a5c021#diff-9272988c09b014f8a2e329f5e295fdb3bef4b75f18a5bd89e92361c23efe1851L40-L47

These fields were not documented anywhere and were not reliable in case of stepdowns/failovers.

Description of Linked Ticket

Currently when dropping a nonexistent database, we return a response that contains information about if the database previously existed or not.
 - On replicaset
 - On sharded cluster

This response is not reliable if a step-down happens during the operation, in fact on step-down the operation is automatically retried on the new replicaset primary. On this new node we don't have any way of assessing previous existence of the database because the old primary could have either already drop it or not.

Moreover the drop database response is not currently documented anywhere.

The goal of this ticket is to simplify the drop database response by not returning any information on the previous state of the database being dropped.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Jeffrey Allen [ 17/Mar/21 ]

Closing as "Won't Fix" because we don't document the specific output of the dropDatabase command.

Generated at Thu Feb 08 08:10:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.