[DOCS-14277] Investigate changes in SERVER-47657: Add 'unique' and 'sparse' parameters to index signature Created: 09/Mar/21 Updated: 13/Nov/23 Resolved: 28/Feb/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 5.0.0, 5.2.0, 5.3.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Ian Fogelman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 1 year, 49 weeks, 2 days ago | ||||||||||||||||
| Epic Link: | DOCSP-9747 | ||||||||||||||||
| Description |
DescriptionDownstream Change Summary unique/sparse index options are now part of index signature. If there's any artifacts which are aware that unique/sparse index options are not part of index signature, probably it need to be modified. Description of Linked Ticket At present, an index's signature - that is, the combination of parameters which uniquely identify the index - is defined by its keypattern and collation. No index can be created if its signature is equivalent to an existing index. We should also add the unique and sparse parameters to the index signature. At present, it is not possible to build a sparse index on a particular key pattern if an existing non-sparse index is already present. Users who wish to move from a full index to a sparse index have little option but to drop the existing index before building the sparse version. A similar situation exists for users who wish to introduce a uniqueness constraint on a field which is already indexed. Workarounds do exist in these situations, but they are ugly and more labour-intensive than should be necessary. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 28/Feb/22 ] |
|
Author: {'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}Message:
|
| Comment by Githook User [ 28/Feb/22 ] |
|
Author: {'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}Message:
|
| Comment by Githook User [ 25/Feb/22 ] |
|
Author: {'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}Message:
|
| Comment by Tess Avitabile (Inactive) [ 16/Feb/22 ] |
|
Thank you! |
| Comment by Jeffrey Allen [ 16/Feb/22 ] |
|
tess.avitabile, you're absolutely right! I'll re-open this and we'll get it prioritized during our team's weekly planning meeting. |
| Comment by Tess Avitabile (Inactive) [ 16/Feb/22 ] |
|
jeffrey.allen, looks like this section needs to be updated: https://docs.mongodb.com/manual/reference/command/createIndexes/#non-collation-and-non-hidden-options |
| Comment by Jeffrey Allen [ 15/Mar/21 ] |
|
I don't think this change has docs impact. Marking as related to |