-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -74,6 +74,11 @@ The :dbcommand:`find` command has the following syntax: | |
} | ||
) | ||
|
||
.. note:: | ||
Since MongoDB 4.4, the :dbcommand:`find` command ignores the | ||
``oplogReplay`` flag. However, if the ``oplogReplay`` flag is set, | ||
QuiqueSanMongo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
the server accepts it for backwards compatibility, but has no effect. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 | ||
|
@@ -421,7 +426,6 @@ When using :ref:`Stable API <stable-api>` V1, the following | |
- ``max`` | ||
- ``min`` | ||
- ``noCursorTimeout`` | ||
- ``oplogReplay`` | ||
- ``returnKey`` | ||
- ``showRecordId`` | ||
- ``tailable`` | ||
|
Uh oh!
There was an error while loading. Please reload this page.