[DOCS-4922] From 2.6 after a collection has been sharded the index of a shard key can be a multi-key index Created: 05/Mar/15  Updated: 27/Jul/16  Resolved: 17/Jun/15

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: mongodb-2.6, mongodb-3.0

Type: Bug Priority: Major - P3
Reporter: Gianfranco Palumbo Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-9620 Index can be made multikey if a prefi... Closed
Participants:
Days since reply: 8 years, 35 weeks ago

 Description   

https://github.com/mongodb/docs/blob/master/source/core/index-multikey.txt#L67



 Comments   
Comment by Githook User [ 17/Jun/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-4922 shard key and multikey index
Branch: master
https://github.com/mongodb/docs/commit/d024680606e394e6deea007dc7d1ac4f7c2aae84

Comment by Githook User [ 17/Jun/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-4922 shard key and multikey index
Branch: v2.6
https://github.com/mongodb/docs/commit/a6d5580484458ebc06d0d21f894bb3705f793208

Comment by Gianfranco Palumbo [ 05/Mar/15 ]

A sharded collection can now have multikey indexes after it has been sharded. However, this is not encouraged as queries that use the multikey indexes will always be slower than normal indexes. Therefore, it is highly recommended to have a dedicated index for the shard key that is not a multikey type if the user wants to use a multikey index on another field.

Generated at Thu Feb 08 07:49:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.