Skip to content

Commit b115e34

Browse files
author
Sam Kleinman
committed
DOCS-362 capped collections behavior clarification
1 parent bf5e68a commit b115e34

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

source/core/indexes.txt

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,15 @@ is a 12-byte unique identifiers suitable for use as the value of an
9494
have an ``_id`` field by default. In 2.2, all capped collections
9595
have an ``_id`` field, except those in the ``local``
9696
:term:`database`. See the :ref:`release notes
97-
<2.2-id-indexes-capped-collections>` for more information.
97+
<2.2-id-indexes-capped-collections>` for more
98+
information.
99+
100+
Additionally, MongoDB does not create indexes on capped collections
101+
by default do not have an index on the ``_id`` field. In the
102+
course of replicating a capped collection, :term:`secondary`
103+
members of the set will create an ``_id`` index. If you specify
104+
``autoIndexId: true`` when creating a capped collection MongoDB
105+
will create an ``_id`` index on this collection.
98106

99107
.. TODO fix the above when a full capped-collection page exists.
100108

0 commit comments

Comments
 (0)