Skip to content

Commit f7451b0

Browse files
committed
Update master
1 parent 50bdbf8 commit f7451b0

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

draft/core/indexes.txt

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -271,8 +271,8 @@ index to locate the document:
271271
Unique Index
272272
~~~~~~~~~~~~
273273

274-
The unique index will cause MongoDB to reject all documents that
275-
contain a duplicate value for the index field. To create a unique index
274+
A unique index will cause MongoDB to reject all documents that
275+
contain a duplicate value for the indexed field. To create a unique index
276276
on the ``user_id`` field of the ``members`` collection, use the
277277
following operation in the :program:`mongo` shell:
278278

@@ -317,8 +317,9 @@ the :program:`mongo` shell:
317317

318318
.. note::
319319

320-
Sparse indexes are not `block-level`_ indexes. Think of them as
321-
dense indexes with a specific filter.
320+
Sparse indexes in MongoDB are not to be confused with `block-level`_
321+
indexes in other databases. Think of them as dense indexes with a
322+
specific filter.
322323

323324
You can combine the sparse index option with the :ref:`unique
324325
indexes <index-type-unique>` option so that :program:`mongod` will
@@ -356,7 +357,7 @@ By default, creating an index is a blocking operation. Building an
356357
index on a large collection of data, the operation can take a long
357358
time to complete. To resolve this issue, the background option can
358359
allow you to continue to use your :program:`mongod` instance during
359-
the index build. Create an index in the background of the ``zipcide``
360+
the index build. Create an index in the background of the ``zipcode``
360361
field of the ``people`` collection using a command that resembles the
361362
following:
362363

@@ -417,8 +418,7 @@ construction:
417418
:dbcommand:`compact` will not run concurrently with a background
418419
index build.
419420

420-
Queries will not use these indexes until the index build is complete
421-
because the index builds in the ``system.indexes`` database.
421+
Queries will not use these indexes until the index build is complete.
422422

423423
.. _index-creation-duplicate-dropping:
424424

@@ -540,6 +540,7 @@ data.
540540

541541
.. TODO insert link to special /core/geospatial.txt documentation
542542
on this topic. once that document exists.
543+
-- TODO short mention of geoHaystack indexes here?
543544

544545
Index Limitations
545546
-----------------
@@ -548,7 +549,7 @@ Be aware of the following current limitations of MongoDB's indexes:
548549

549550
- A collection may have no more than :ref:`64 indexes <limit-number-of-indexes-per-collection>`.
550551

551-
- Indexed items can have no more than :ref:`1024 bytes <limit-index-size>`.
552+
- Index keys can be no larger than :ref:`1024 bytes <limit-index-size>`.
552553

553554
This includes the field value or values, the field name or names,
554555
and the :term:`namespace`.

0 commit comments

Comments
 (0)