Skip to content

Commit 4c7b4c2

Browse files
DOCSP-31389 Capped Collections with TTL (#4662)
* Quick fix, removed statements that TTL index aren't supported on capped collections * Internal review * Fixed comma * Rebuild
1 parent 849ed95 commit 4c7b4c2

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

source/core/capped-collections.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,13 @@ by overwriting the oldest documents in the collection.
2222
See :method:`~db.createCollection()` or :dbcommand:`create`
2323
for more information on creating capped collections.
2424

25-
.. tip::
25+
As an alternative to capped collections, consider :ref:`TTL (Time To
26+
Live) indexes <index-feature-ttl>`. TTL indexes allow you to expire and
27+
remove data from normal collections based on the value of a date-typed
28+
field and a TTL value for the index. You can also use a TTL index on a
29+
capped collection to remove expired documents even if the capped
30+
collection hasn't exceeded its size limit. For details, :ref:`ttl-collections`.
2631

27-
As an alternative to capped collections, consider MongoDB's
28-
:ref:`TTL (Time To Live) indexes <index-feature-ttl>`. As
29-
described in :ref:`ttl-collections`, these indexes allow you
30-
to expire and remove data from normal collections based on the value
31-
of a date-typed field and a TTL value for the index.
3232

3333
Behavior
3434
--------

0 commit comments

Comments
 (0)