Skip to content

DOCSP-43405-msg-oplogReplay-find-command #6295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 20, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion source/reference/command/find.txt
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,11 @@ The :dbcommand:`find` command has the following syntax:
}
)

.. note::
Since MongoDB 4.4, the ``find`` command ignores the
``oplogReplay`` flag. If the ``oplogReplay`` flag is set,
the server accepts it for backwards compatibility, but has no effect.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll defer to external review on this, but I'm wondering if we even need this note. Since we've removed all other docs for this command I'm wondering if calling this out will just be more confusing than helpful to users. Just feels slightly odd to me to call out this flag with no explanation of what it is / does.

.. _find-cmd-fields:

Command Fields
Expand Down Expand Up @@ -421,7 +426,6 @@ When using :ref:`Stable API <stable-api>` V1, the following
- ``max``
- ``min``
- ``noCursorTimeout``
- ``oplogReplay``
- ``returnKey``
- ``showRecordId``
- ``tailable``
Expand Down