[DOCS-2609] Correct Documentation of Unique Indexs for Sharded Collections Created: 28/Jan/14 Updated: 17/Mar/14 Resolved: 21/Feb/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.1 |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Mathias Stearn | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/tutorial/enforce-unique-keys-for-sharded-collections/ |
||
| Participants: | |
| Days since reply: | 9 years, 48 weeks, 2 days ago |
| Description |
|
footnote 1 makes it seem like we let you create a unique index on a sharded collection and just fail to enforce it. We don't. Creating new unique indexes will fail, and we refuse to shard collections with unique indexes on fields other than _id. The footnote as-is (and much of this page) only applies to the _id index. Also the Warning should probably be presented as a 3rd option: using guaranteed unique identifiers. |
| Comments |
| Comment by Githook User [ 17/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 17/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 21/Feb/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 21/Feb/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |