Skip to content

Commit eea48f0

Browse files
Clarify shard key index cannot be a partial index. (#5834)
* Clarify shard key index cannot be a partial index. * slight refactoring * Update source/includes/limits-sharding-index-type.rst Co-authored-by: Jeff Allen <[email protected]> * review changes * final internal review changes * add link to partial index --------- Co-authored-by: Jeff Allen <[email protected]>
1 parent 784f90f commit eea48f0

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

source/includes/limits-sharding-index-type.rst

+10-8
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,15 @@ key, a compound index that starts with the shard key and specifies
33
ascending order for the shard key, or a :ref:`hashed index
44
<index-type-hashed>`.
55

6-
A :term:`shard key` index cannot be a descending index on the shard key.
7-
Additionally, a shard key index cannot be any of the following index
8-
types:
9-
10-
- :ref:`multikey <index-type-multikey>`
11-
- :ref:`text <index-type-text>`
12-
- :ref:`geospatial <index-feature-geospatial>`
13-
- :ref:`wildcard <wildcard-index-core>`
6+
A :term:`shard key` index *cannot* be:
7+
8+
- A descending index on the shard key
9+
- A :ref:`partial index <index-type-partial>`
10+
- Any of the following index types:
11+
12+
- :ref:`Geospatial <index-feature-geospatial>`
13+
- :ref:`Multikey <index-type-multikey>`
14+
- :ref:`Text <index-type-text>`
15+
- :ref:`Wildcard <wildcard-index-core>`
1416

1517
.. COMMENT seealso extracts-geospatial-index-shard-key-restriction.yaml

0 commit comments

Comments
 (0)