DOCSP-27277 - EOL Reference Cleanup for Database Commands (#2327) (#2… (#2518)

* DOCSP-27277 - EOL Reference Cleanup for Database Commands (#2327) (#2515)

* DOCSP-27277 - EOL Reference Cleanup for Database Commands (#2327)

* DOCSP-27277 EOL version reference cleanup for Database Commands

* Refactors version references to use directive

* Version cleanup createIndexes and serverStatus

* EOL version cleanup for currentOp

* EOL version cleanup for currentOp

* EOL version cleanup for listDatabases

* EOL version cleanup for listDatabases

* EOL version cleanup for listCollections

* EOL version cleanup for listCollections

* EOL version cleanup for usersInfo

* EOL reference fixes for dbHash and updateUser

* EOL reference fixes for killOp replSetSyncFrom

* Fixes per Kyle Suarez

* Fixes per Kyle Suarez.

Co-authored-by: Kyle Suarez <[email protected]>

---------

Co-authored-by: Kyle Suarez <[email protected]>

* Reverts text to fix build errors

* Fixes indentation from cherry-pick

---------

Co-authored-by: Kyle Suarez <[email protected]>

* Fixes build error

---------

Co-authored-by: Kyle Suarez <[email protected]>

Author: kennethdyer

source/includes/extracts-command-field.yaml

@@ -1,8 +1,6 @@
 ref: _command-field
 content: |
 
-  .. versionchanged:: 3.6
-
   A document containing the full command object associated with this
   operation. 
 

source/includes/fact-voting-node-sync-incompatibility.rst

@@ -1,3 +1,2 @@
-MongoDB 3.2 replica set members with :rsconf:`1 vote
-<members[n].votes>` cannot sync from members with  :rsconf:`0 votes
-<members[n].votes>`.
+Replica set members with :rsconf:`1 vote <members[n].votes>` 
+cannot sync from members with  :rsconf:`0 votes <members[n].votes>`.

source/reference/command/createIndexes.txt

@@ -83,29 +83,25 @@ Definition
 
         - Optional. A document expressing the :doc:`write concern
           </reference/write-concern>`. Omit to use the default write concern.
-          
-          .. versionadded:: 3.4
-          
-          
-   
+
    .. _createIndexes-options:
 
    Each document in the ``indexes`` array can take the following fields:
-
+  
    .. list-table::
       :header-rows: 1
       :widths: 20 20 80
-   
+    
       * - Field
-   
+    
         - Type
-   
+    
         - Description
-   
+    
       * - ``key``
-   
+    
         - document
-   
+    
         - 
           Specifies the index's fields. For each field, specify a key-value pair
           in which the key is the name of the field to index and the value is
@@ -118,7 +114,7 @@ Definition
           MongoDB supports several different index types including
           :ref:`text <index-feature-text>`, :ref:`geospatial
           <index-feature-geospatial>`, and :ref:`hashed
-          <index-type-hashed>` indexes. See :ref:`index types <index-types>`
+          indexes <index-type-hashed>`. See :ref:`index types <index-types>`
           for more information.
 
           .. versionchanged:: 4.2
@@ -166,29 +162,29 @@ Definition
 
 
 
-   
+    
       * - ``name``
-   
+    
         - string
-   
+    
         - A name that uniquely identifies the index.
 
 
-   
+    
       * - ``background``
-   
+    
         - boolean
-   
+    
         - Optional. *Deprecated in MongoDB 4.2.*
 
           .. include:: /includes/extracts/4.2-index-background.rst
 
 
-   
+    
       * - ``unique``
-   
+    
         - boolean
-   
+    
         - Optional. Creates a unique index so that the collection will not accept
           insertion or update of documents where the index key value matches an existing
           value in the index.
@@ -197,16 +193,16 @@ Definition
           Specify ``true`` to create a unique index. The
           default value is ``false``.
 
-          The option is *unavailable* for :doc:`hashed </core/index-hashed>`
+          The option is *unavailable* for :ref:`hashed <index-hashed-index>`
           indexes.
 
 
 
-   
+    
       * - ``partialFilterExpression``
-   
+    
         - document
-   
+    
         - Optional. If specified, the index only references documents that match the
           filter expression. See :doc:`/core/index-partial` for more information.
 
@@ -218,50 +214,44 @@ Definition
           You can specify a ``partialFilterExpression`` option for all MongoDB
           :ref:`index types <index-types>`.
 
-          .. versionadded:: 3.2
 
 
-          
-   
+    
       * - ``sparse``
-   
+    
         - boolean
-   
+    
         - Optional. If ``true``, the index only references documents with the specified
           field. These indexes use less space but behave differently in some
           situations (particularly sorts). The default value is ``false``.
           See :doc:`/core/index-sparse` for more information.
-
+    
           The following index types are sparse by default and ignore
           this option:
-
+    
           - :doc:`2dsphere </core/2dsphere>`
           - :doc:`2d </core/2d>`
           - :doc:`geoHaystack </core/geohaystack>`
-          - :doc:`text </core/index-text>`
-
+          - :ref:`text <index-feature-text>`
+    
           For a compound index that includes ``2dsphere`` index key(s)
           along with keys of other types, only the ``2dsphere`` index
           fields determine whether the index references a document.
-
-          .. versionchanged:: 3.2 
-
-             Starting in MongoDB 3.2, MongoDB provides the option to create
-             :ref:`partial indexes <index-type-partial>`. Partial indexes
-             offer a superset of the functionality of sparse indexes. If you
-             are using MongoDB 3.2 or later, :ref:`partial indexes
-             <index-type-partial>` should be preferred over sparse indexes.
-   
+    
+    
+          MongoDB provides the option to create
+          :ref:`partial indexes <index-type-partial>`. These
+          offer a superset of the functionality of sparse indexes
+          and are preferred instead.
+    
       * - ``expireAfterSeconds``
-   
+    
         - integer
 
         - Optional. Specifies a value, in seconds, as a :term:`TTL` to control how long
           MongoDB retains documents in this collection. See
           :doc:`/tutorial/expire-data` for more information on this
           functionality. This applies only to :term:`TTL` indexes.
-          
-          
 
       * - ``storageEngine``
 
@@ -448,11 +438,9 @@ Definition
 Considerations
 --------------
 
-.. versionchanged:: 3.2
-
-   MongoDB disallows the creation of :ref:`version 0
-   <3.2-version-0-indexes>` indexes. To upgrade existing version 0
-   indexes, see :ref:`3.2-version-0-indexes`.
+MongoDB disallows the creation of :ref:`version 0
+<3.2-version-0-indexes>` indexes. To upgrade existing version 0
+indexes, see :ref:`3.2-version-0-indexes`.
 
 Index Names
 ~~~~~~~~~~~
@@ -518,9 +506,7 @@ Concurrency
 Memory Usage Limit
 ~~~~~~~~~~~~~~~~~~
 
-.. versionchanged:: 3.4
-
-   .. include:: /includes/fact-index-build-default-memory-limit.rst
+.. include:: /includes/fact-index-build-default-memory-limit.rst
 
 
 Index Options

source/reference/command/currentOp.txt

@@ -85,7 +85,7 @@ On systems running with :setting:`~security.authorization`, the user
 must have access that includes the :authaction:`inprog` privilege
 action.
 
-Starting in 3.2.9, users can use
+Users can use
 ``$ownOps`` on :binary:`~bin.mongod` instances to view their own
 operations without the :authaction:`inprog` privilege action.
 
@@ -125,8 +125,6 @@ Write Operations Waiting for a Lock
 The following example returns information on all write operations that
 are waiting for a lock:
 
-.. versionchanged:: 3.6
-
 .. code-block:: javascript
 
    db.adminCommand(
@@ -179,8 +177,6 @@ database ``db1`` that have been running longer than 3 seconds:
 Active Indexing Operations
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionchanged:: 3.6
-
 The following example returns information on index creation operations:
 
 .. code-block:: javascript
@@ -307,8 +303,6 @@ Output Fields
 
    Only present if the operation is part of a multi-document transaction.
 
-   .. versionadded:: 4.0
-
    .. data:: currentOp.transaction.parameters
 
       A document that contains information on multi-document
@@ -317,25 +311,19 @@ Output Fields
       Only present if the operation is part of a multi-document
       transaction.
 
-      .. versionadded:: 4.0
-
       .. data:: currentOp.transaction.parameters.txnNumber
 
          The transaction number.
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0
-
       .. data:: currentOp.transaction.parameters.autocommit
 
          A boolean flag that indicates if autocommit is on for the
          transaction.
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0.2
-
       .. data:: currentOp.transaction.parameters.readConcern
 
          The :ref:`read concern <transactions-read-concern>` for the
@@ -347,25 +335,19 @@ Output Fields
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0.2
-
       .. data:: currentOp.transaction.readTimestamp
 
          The timestamp of the snapshot being read by the operations in
          the transaction.
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0.2
-
       .. data:: currentOp.transaction.startWallClockTime
 
          The date and time (with time zone) of the transaction start.
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0.2
-
       .. data:: currentOp.transaction.timeOpenMicros
 
          The duration of the transaction in microseconds.
@@ -378,8 +360,6 @@ Output Fields
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0.2
-
       .. data:: currentOp.transaction.timeActiveMicros
 
          The total amount of time that the transaction has been active;
@@ -394,8 +374,6 @@ Output Fields
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0.2
-
       .. data:: currentOp.transaction.timeInactiveMicros
 
          The total amount of time that the transaction has been
@@ -424,8 +402,6 @@ Output Fields
 
          Only present if the operation is part of a multi-document transaction.
 
-         .. versionadded:: 4.0.2
-
 .. data:: currentOp.twoPhaseCommitCoordinator
 
    Information on either:

source/reference/command/dbHash.txt

@@ -115,8 +115,6 @@ The command returns a document with the following fields:
 
      - An array that lists the capped collections.
 
-       .. versionadded:: 4.0
-
    * - ``uuids``
 
      - A document with the collections and their corresponding UUID values.
@@ -129,8 +127,6 @@ The command returns a document with the following fields:
              ...
           }
 
-       .. versionadded:: 4.0
-
    * - ``md5``
      - The aggregate hash value for these collections.
 

source/reference/command/killOp.txt

@@ -67,14 +67,13 @@ On systems running with :setting:`~security.authorization`, to kill
 operations not owned by the user, the user must have access that
 includes the :authaction:`killop` privilege action.
 
-.. versionchanged:: 3.2.9
-   On :binary:`~bin.mongod` instances, users can kill their own operations
-   even without the :authaction:`killop` privilege action.
+On :binary:`~bin.mongod` instances, users can kill their own operations
+even without the :authaction:`killop` privilege action.
 
 Sharded Cluster
 ---------------
 
-Starting in MongoDB 4.0, the :dbcommand:`killOp` command can be run on
+The :dbcommand:`killOp` command can be run on
 a :binary:`~bin.mongos` and can kill queries (i.e. read operations)
 that span shards in a cluster. The :dbcommand:`killOp` command from the
 :binary:`~bin.mongos` does not propagate to the shards when the