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

kennethdyer · ksuarz · web-flow · commit 361c19e54cb7 · 2023-02-02T17:43:41.000-08:00
* 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 <ksuarz@gmail.com> --------- Co-authored-by: Kyle Suarez <ksuarz@gmail.com>
diff --git a/source/includes/extracts-command-field.yaml b/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. 
 
diff --git a/source/includes/fact-voting-node-sync-incompatibility.rst b/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>`.
diff --git a/source/reference/command/createIndexes.txt b/source/reference/command/createIndexes.txt
@@ -301,13 +301,11 @@ Each document in the ``indexes`` array can take the following fields:
        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``
  
@@ -521,11 +519,9 @@ Each document in the ``indexes`` array can take the following fields:
 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
 ~~~~~~~~~~~
@@ -622,9 +618,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
diff --git a/source/reference/command/currentOp.txt b/source/reference/command/currentOp.txt
@@ -94,7 +94,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.
 
@@ -136,8 +136,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(
@@ -190,8 +188,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
@@ -322,8 +318,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
@@ -332,25 +326,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
@@ -362,25 +350,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.
@@ -393,8 +375,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;
@@ -409,8 +389,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
@@ -439,8 +417,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:
diff --git a/source/reference/command/dbHash.txt b/source/reference/command/dbHash.txt
@@ -118,8 +118,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.
@@ -132,8 +130,6 @@ The command returns a document with the following fields:
              ...
           }
 
-       .. versionadded:: 4.0
-
    * - ``md5``
      - The aggregate hash value for these collections.
 
diff --git a/source/reference/command/killOp.txt b/source/reference/command/killOp.txt
@@ -81,14 +81,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
diff --git a/source/reference/command/listCollections.txt b/source/reference/command/listCollections.txt
@@ -76,8 +76,6 @@ The command can take the following optional fields:
          filter based on a collection's name and type. No other fields are
          available.
       
-      .. versionadded:: 4.0
-      
   * - ``authorizedCollections``
     - boolean
     - Optional. A flag, when set to ``true`` and used with ``nameOnly: true``, that
@@ -105,8 +103,6 @@ The command can take the following optional fields:
       command when access control is enforced. Otherwise, the user is
       unauthorized to run the command.
       
-      .. versionadded:: 4.0
-      
   * - ``comment``
     - any
     - .. include:: /includes/extracts/comment-content.rst
@@ -129,8 +125,6 @@ set.
 Locks
 ~~~~~
 
-.. versionchanged:: 4.0
-
 The :dbcommand:`listCollections` command takes Intent Shared lock on the
 database. In previous versions, the command takes Shared lock on the
 database.
@@ -163,11 +157,6 @@ Required Access
 
 .. include:: /includes/extracts/listCollections-auth-show-collections.rst
 
-Earlier MongoDB Versions
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. include:: /includes/extracts/listCollections-auth-show-collections-earlier-versions.rst
-
 .. _list-collection-output:
 
 Output
diff --git a/source/reference/command/listDatabases.txt b/source/reference/command/listDatabases.txt
@@ -82,8 +82,6 @@ The command can take the following optional fields:
        
        For more information, see :ref:`listDatabases-behavior`.
        
-       .. versionadded:: 4.0.5
-       
    * - ``comment``
      - any
      - .. include:: /includes/extracts/comment-content.rst
@@ -95,63 +93,13 @@ The command can take the following optional fields:
 Behavior
 --------
 
-When :ref:`authentication <authentication>` is enabled:
-
-.. note::
- 
-   For :binary:`~bin.mongosh` connected to earlier
-   versions of MongoDB deployment (e.g. 3.6.10), 
-   
-   - If the user has :authaction:`listDatabases` action on the cluster
-     resource, ``show dbs`` returns all databases.
-
-   - If the user does not have :authaction:`listDatabases` action on
-     the cluster resource, ``show dbs`` returns only the databases for
-     which the user has privileges (including those databases for which
-     the user has privileges on specific collections).
-
-.. tabs::
-
-   tabs:
-
-   - id: mongodb-4.0.6
-     name:  "MongoDB 4.0.6+"
-     content: |
-        For MongoDB 4.0.6+, the :dbcommand:`listDatabases` command
-        returns different values based on the privileges assigned to
-        the user who executes the command and the
-        ``authorizedDatabases`` command option:
-
-        .. include:: /includes/extracts/listDatabases-auth-privileges-4.0.6.rst
-
-   - id: mongodb-4.0.5
-     name:  "MongoDB 4.0.5"
-     content: |
-
-        For MongoDB 4.0.5, the :dbcommand:`listDatabases` command
-        returns different values based on the privileges assigned to
-        the user who executes the command and the
-        ``authorizedDatabases`` command option:
-
-        .. include:: /includes/extracts/listDatabases-auth-privileges-4.0.5.rst
-
-   - id: mongodb-4.0.4
-     name:  "MongoDB 4.0.0-4.0.4"
-     content: |
-
-        For MongoDB 4.0.0-4.0.4, the :dbcommand:`listDatabases` command
-        returns different values based on the privileges assigned to
-        the user who executes the command.
+When :ref:`authentication <authentication>` is enabled,
+the :dbcommand:`listDatabases` command returns different values based on 
+the privileges assigned to the user who executes the command and the
+``authorizedDatabases`` command option:
 
-        - If the user has the :authaction:`listDatabases` privilege
-          action on the cluster, the :dbcommand:`listDatabases` command
-          returns a list of all existing databases.
+.. include:: /includes/extracts/listDatabases-auth-privileges-4.0.6.rst
 
-        - If the user does not have the :authaction:`listDatabases`
-          privilege action on the cluster, the
-          :dbcommand:`listDatabases` command only returns a list of
-          databases for which the user has the :authaction:`find`
-          action.
 
 Client Disconnection
 ~~~~~~~~~~~~~~~~~~~~~
diff --git a/source/reference/command/replSetSyncFrom.txt b/source/reference/command/replSetSyncFrom.txt
@@ -20,9 +20,7 @@ Description
    patterns and in situations where a set member is not replicating
    from the desired host.
 
-   .. versionchanged:: 3.2
-
-      .. include:: /includes/fact-voting-node-sync-incompatibility.rst
+   .. include:: /includes/fact-voting-node-sync-incompatibility.rst
 
    Run :dbcommand:`replSetSyncFrom` in the ``admin`` database.
 
@@ -57,9 +55,7 @@ The command takes the following field:
      - The name and port number of the replica set member that this member
        should replicate from. Use the ``[hostname]:[port]`` form.
        
-       .. versionchanged:: 3.2
-       
-          .. include:: /includes/fact-voting-node-sync-incompatibility.rst
+       .. include:: /includes/fact-voting-node-sync-incompatibility.rst
            
 Behavior
 --------
diff --git a/source/reference/command/serverStatus.txt b/source/reference/command/serverStatus.txt
diff --git a/source/reference/command/updateUser.txt b/source/reference/command/updateUser.txt
diff --git a/source/reference/command/usersInfo.txt b/source/reference/command/usersInfo.txt
