DOCS-11758: drop takes options document

Author: kay-kim

source/reference/command/drop.txt

@@ -17,15 +17,37 @@ drop
 
    .. code-block:: javascript
 
-        { drop: <collection_name> }
+      { drop: <collection_name>, writeConcern: <document>}
+
+   The command takes the following fields:
+
+   .. list-table::
+      :header-rows: 1
+      :widths: 20 80
+
+      * - Field
+        - Description
+
+      * - drop
+        - The name of the collection to drop.
+
+      * - writeConcern
+
+        - Optional. A document expressing the :doc:`write concern
+          </reference/write-concern>` of the :dbcommand:`drop` command.
+          Omit to use the default write concern.
+  
 
    The :binary:`~bin.mongo` shell provides the equivalent helper method
    :method:`db.collection.drop()`.
 
-   This command also removes any indexes associated with the dropped
-   collection.
+Behavior
+--------
+
+This command also removes any indexes associated with the dropped
+collection.
 
-   .. warning::
+.. warning::
 
-      This command obtains a write lock on the affected database and
-      will block other operations until it has completed.
+   This command obtains a write lock on the affected database and
+   will block other operations until it has completed.

source/reference/method/db.collection.drop.txt

@@ -15,7 +15,7 @@ db.collection.drop()
 Definition
 ----------
 
-.. method:: db.collection.drop()
+.. method:: db.collection.drop(<options>)
 
    Removes a collection or :doc:`view </core/views>` from the database.
    The method also removes any indexes associated with the dropped
@@ -24,13 +24,33 @@ Definition
 
    :method:`db.collection.drop()` has the form:
 
+   .. versionchanged:: 4.0
+
+      :method:`db.collection.drop()` accepts an options document.
+
    .. code-block:: javascript
 
-      db.collection.drop()
+      db.collection.drop( { writeConcern: <document> } )
+
+   :method:`db.collection.drop()` takes an optional document with the
+   following field:
+
+   .. list-table::
+      :header-rows: 1
+      :widths: 20 80
 
-   :method:`db.collection.drop()` takes no arguments and will produce
-   an error if called with any arguments.
+      * - Field
+        - Description
 
+      * - writeConcern
+
+        - Optional. A document expressing the :doc:`write concern
+          </reference/write-concern>` of the
+          :method:`db.collection.drop()` operation. Omit to use the
+          default write concern.
+
+          .. versionadded:: 4.0
+  
    :returns:
      - ``true`` when successfully drops a collection.
      - ``false`` when collection to drop does not exist.
@@ -44,9 +64,27 @@ will block other operations until it has completed.
 Example
 -------
 
+Drop a Collection Using Default Write Concern
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 The following operation drops the ``students`` collection in the
 current database.
 
 .. code-block:: javascript
 
    db.students.drop()
+
+Drop a Collection Using ``w: "majority"`` Write Concern
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. versionchanged:: 4.0
+
+   :method:`db.collection.drop()` accepts an options document.
+
+The following operation drops the ``students`` collection in the
+current database. The operation uses the :writeconcern:`"majority"`
+write concern:
+
+.. code-block:: javascript
+
+   db.students.drop( { writeConcern: "majority" } )

source/release-notes/4.0.txt

@@ -475,19 +475,22 @@ Aggregation
 Commands
 ~~~~~~~~
 
-- Added the following option to :dbcommand:`listCollections` command
-  and the :binary:`~bin.mongo` shell helper
-  :method:`db.getCollectionInfos()`:
+- The command :dbcommand:`listCollections` and its :binary:`~bin.mongo`
+  shell helper :method:`db.getCollectionInfos()` accepts the following
+  option:
 
   - ``nameOnly`` to return only the collection names and types (which
     does not require collection locks).
 
-- The command :dbcommand:`serverStatus` and the :binary:`~bin.mongo`
+- The command :dbcommand:`serverStatus` and its :binary:`~bin.mongo`
   shell helper :method:`db.serverStatus()` includes
   :serverstatus:`shardingStatistics` in its output. The
   :serverstatus:`shardingStatistics` includes data on metadata refresh
   on sharded clusters.
 
+- The :binary:`~bin.mongo` shell helper :method:`db.collection.drop()`
+  accepts the write concern option.
+
 Network Layer Improvements
 ~~~~~~~~~~~~~~~~~~~~~~~~~~