Skip to content

DOCS-14375 add capped collection note to 5.0 changelog #5927

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
Show file tree
Hide file tree
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
2 changes: 2 additions & 0 deletions source/core/capped-collections.txt
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,8 @@ result, queries do not need an index to return documents in insertion
order. Without this indexing overhead, capped collections can support
higher insertion throughput.

.. _capped_collections_remove_documents:

Automatic Removal of Oldest Documents
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
9 changes: 9 additions & 0 deletions source/release-notes/5.0.txt
Original file line number Diff line number Diff line change
Expand Up @@ -661,6 +661,15 @@ Transactions
General Improvements
--------------------

Capped Collection Deletes Process On Secondaries
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Starting in MongoDB 5.0, the
:ref:`implicit delete operations <capped_collections_remove_documents>`
of :doc:`replica set </replication>`
:term:`capped collections <capped collection>` are processed by
the :doc:`secondary members </core/replica-set-secondary/>`.

Execution Plan Statistics for Query with ``$lookup`` Pipeline Stage
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down