DOCSP-25224 eol cleanup v4.2 (#2148)

* DOCSP-25224 EOL Version Cleanup of mongosh Methods (#1901) (#2146) (#2147)

* DOCSP-25224 EOL Version Cleanup of mongosh Methods (#1901)

* Fixes build error

* Fixes build errors

* Fixes build errors

* Fixes build errors

* Fixes build errors

* Build error

Author: kennethdyer

source/faq/concurrency.txt

@@ -385,10 +385,6 @@ than one database:
    * - Operation
      -
 
-   * - :method:`db.copyDatabase()`
-     - This operation obtains a global (W) exclusive lock and blocks
-       other operations until it finishes.
-
    * - | :dbcommand:`reIndex`
        | :method:`db.collection.reIndex()` 
      - .. versionchanged:: 4.2

source/includes/change-stream/resume-after.rst

@@ -0,0 +1,9 @@
+
+.. note::
+
+   You cannot use ``resumeAfter`` to resume a change stream after an
+   :ref:`invalidate event <change-event-invalidate>` (for example, a collection
+   drop or rename) closes the stream. Starting in MongoDB 4.2, you can use
+   :ref:`startAfter <change-stream-start-after>` to start a new change
+   stream after an :ref:`invalidate event <change-event-invalidate>`.
+

source/includes/cursor-index-use.rst

@@ -0,0 +1,8 @@
+
+.. note:: Index Use
+
+   To use an index with the :method:`~cursor.max()` method, you must use the
+   :method:`~cursor.hint()` method to specify the index you want to use,
+   exept when the :method:`~db.collection.find()` query is an equality
+   condition on the ``_id`` field.
+

source/includes/extracts-listCollections-auth.yaml

@@ -14,7 +14,7 @@ content: |
    The built-in role :authrole:`read` provides the privilege to run
    :dbcommand:`listCollection` for a specific database.
 
-   Starting in version 4.0, however, user without the required privilege
+   Users without the required privilege
    can run the command with **both** ``authorizedCollections`` and
    ``nameOnly`` options set to ``true``. In this case, the command returns
    just the name and type of the collection(s) to which the user has
@@ -48,8 +48,7 @@ content: |
 ref: listCollections-auth-show-collections
 content: |
 
-   Starting in version 4.0 of the :binary:`~bin.mongo` shell, ``show
-   collections`` is equivalent to:
+   The ``mongo`` shell, ``show collections`` is equivalent to:
 
    .. code-block:: javascript
 
@@ -79,8 +78,7 @@ content: |
 ref: listCollections-auth-showCollectionNames
 content: |
 
-   Starting in version 4.0 of the :binary:`~bin.mongo` shell,
-   :method:`db.getCollectionNames()` is equivalent to:
+   The :method:`db.getCollectionNames()` is equivalent to:
 
    .. code-block:: javascript
 

source/includes/extracts-sessions.yaml

@@ -110,8 +110,8 @@ content: |
 ref: sessions-cursor-timeout
 content: |
 
-   Starting in MongoDB 3.6, MongoDB drivers and the :binary:`~bin.mongo`
-   shell associate all operations with a :doc:`server session
+   MongoDB drivers and :binary:`~bin.mongosh`
+   associate all operations with a :doc:`server session
    </reference/server-sessions>`, with the exception of unacknowledged
    write operations. For operations not explicitly associated with a
    session (i.e. using :method:`Mongo.startSession()`), MongoDB drivers

source/includes/extracts-syncFrom.yaml

@@ -3,14 +3,9 @@ content: |
    Sync Logic
    ~~~~~~~~~~
 
-   .. versionchanged:: 3.4
-
    If an initial sync operation is in progress when you run
    {{syncfrom}}, {{syncfrom}} stops the in-progress initial sync and
-   restarts the sync process with the new target. In previous versions,
-   if you run {{syncfrom}} during initial sync, MongoDB produces no
-   error messages, but the sync target will not change until after the
-   initial sync operation.
+   restarts the sync process with the new target. 
 
    Only modify the default sync logic as needed, and always exercise
    caution. 

source/includes/extracts-zoned-sharding.yaml

@@ -66,8 +66,7 @@ content: |
 ref: zoned-sharding-drop-collection-change
 content: |
 
-   Starting in MongoDB 4.0.2, dropping a collection deletes its
-   associated zone/tag ranges.
+   Dropping a collection deletes its associated zone/tag ranges.
 
 ...
 

source/includes/fact-aggregate-readConcern.rst

@@ -2,5 +2,3 @@ Starting in MongoDB 4.2, you can specify :doc:`read concern
 </reference/read-concern>` level :readconcern:`"majority"` for an
 aggregation that includes an :pipeline:`$out` stage.
 
-In MongoDB 4.0 and earlier, you cannot include the :pipeline:`$out`
-stage to use :readconcern:`"majority"` read concern for the aggregation.

source/includes/fact-index-resource-lock.rst

@@ -0,0 +1,10 @@
+
+MongoDB uses an optimized build process that obtains and holds an exclusive 
+lock on the specified collection at the start and end of the index build. All
+subsequent operations on the collection must wait until |method| releases
+the exclusive lock. |method| allows interleaving read and write
+operations during the majority of the index build.
+
+For more information on the locking behavior of |method|, see
+:ref:`index-operations`.
+

source/includes/fact-retryable-writes-failover-election.rst

@@ -1,10 +1,10 @@
 Your application connection logic should include tolerance for automatic
-failovers and the subsequent elections. Starting in MongoDB 3.6, MongoDB drivers
+failovers and the subsequent elections. MongoDB drivers
 can detect the loss of the primary and automatically 
 :ref:`retry certain write operations <retryable-writes>` a single time, 
 providing additional built-in handling of automatic failovers and elections:
 
-- MongoDB 4.2+ compatible drivers enable retryable writes by default
+.. versionchanged:: 4.2
+
+Starting in MongoDB 4.2, compatible drivers enable retryable writes by default
 
-- MongoDB 4.0 and 3.6-compatible drivers must explicitly enable
-  retryable writes by including :urioption:`retryWrites=true <retryWrites>` in the :ref:`connection string <mongodb-uri>`.