DOCS-12912 Ignore value of oplogReplay option

Author: kanchana-mongodb

source/reference/command/find.txt

@@ -30,10 +30,13 @@ Definition
 Syntax
 ------
 
-.. versionchanged:: 4.2
+.. versionchanged:: 4.4
 
-   MongoDB removes the deprecated ``maxScan`` option to the
-   :dbcommand:`find` command. Use the ``maxTimeMS`` option instead.
+   MongoDB deprecates the ``oplogReplay`` option to the :dbcommand:`find` 
+   command. The optimization enabled by this flag in previous versions now 
+   happens automatically for eligible queries on the oplog. Therefore, 
+   you don't need to specify this flag. If specified, the server accepts 
+   the flag for backwards compatibility, but the flag has no effect.
 
 The :dbcommand:`find` command has the following syntax:
 
@@ -67,6 +70,8 @@ The :dbcommand:`find` command has the following syntax:
       }
    )
 
+.. _find-cmd-fields:
+
 Command Fields
 ~~~~~~~~~~~~~~
 
@@ -284,13 +289,14 @@ The command accepts the following fields:
 
      - boolean
 
-     - Optional. An internal command for replaying a :ref:`replica set's oplog
+     - .. deprecated:: 4.4
+     
+       Optional. An internal command for replaying a :ref:`replica set's oplog
        <replica-set-oplog>`.
 
-       To use ``oplogReplay``, the ``find`` field must refer to a
-       :doc:`capped collection </core/capped-collections>` and you must
-       provide a ``filter`` option comparing the ``ts`` document field to a
-       :data:`timestamp` using one of the following comparison operators:
+       To use ``oplogReplay``, the ``find`` field must provide a ``filter`` 
+       option comparing the ``ts`` document field to a :data:`timestamp` using 
+       one of the following comparison operators:
 
        * :expression:`$gte`
        * :expression:`$gt`
@@ -306,11 +312,18 @@ The command accepts the following fields:
             oplogReplay: true,
             filter: { ts: { $gte: new Timestamp(1514764800, 0) } } }
 
-       .. versionchanged:: 3.6
-       
-          :expression:`$eq` is now supported.
-       
-       
+       .. admonition:: Deprecated
+          :class: note
+
+          .. versionchanged:: 4.4
+
+          Starting in MongoDB 4.4, the ``oplogReplay`` field is deprecated. 
+          ``find`` fields that use the :expression:`$gte`, :expression:`$gt`, 
+          or :expression:`$eq` ``filter`` predicated on the ``ts`` field 
+          will automatically utilize the storage format of the :ref:`replica 
+          set's oplog <replica-set-oplog>` to execute the command more 
+          efficiently. If specified, the server accepts the ``oplogReplay`` 
+          flag for backwards compatibility, but the flag has no effect. 
 
    * - ``noCursorTimeout``
 

source/reference/mongodb-wire-protocol.txt

@@ -361,11 +361,13 @@ collection. The format of the OP_QUERY message is:
          invalid at some point (CursorNotFound) – for example if the
          final object it references were deleted.
 
-       - ``2`` corresponds to SlaveOk.Allow query of replica slave.
+       - ``2`` corresponds to SlaveOk. Allow query of replica slave.
          Normally these return an error except for namespace "local".
 
-       - ``3`` corresponds to OplogReplay. Internal replication use
-         only - driver should not set.
+       - ``3`` corresponds to OplogReplay. Starting in MongoDB 4.4, you 
+         need not specify this flag because the optimization  
+         automatically happens for eligible queries on the oplog. See 
+         :ref:`oplogReplay <find-cmd-fields>` for more information.
 
        - ``4`` corresponds to NoCursorTimeout. The server normally
          times out idle cursors after an inactivity period (10 minutes)