[DOCS-14369] Investigate changes in SERVER-47659: Add 'wildcardProjection' parameter to index signature Created: 19/Apr/21 Updated: 13/Nov/23 Resolved: 23/Nov/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0, 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: | 2 years, 11 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-15042 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
DescriptionDownstream Change Summary The wildcardProjection index option is now part of the index signature test unlike v4.4. To achieve this behavior, we're normalizing wildcardProjection option if it's not empty before creating an {"$**": 1} wildcard index. For example, {"$**": 1} {wildcardProjection: {a: 1}} is normalized to {"$**": 1} {wildcardProjection: {a: true, _id: false}}, which may be visibly different from what a user exactly specified. 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 wildcardProjection parameter to the index signature. At present, we allow any number of wildcard indexes to be built using the {"field.path.$**": 1} notation, but we do not allow multiple wildcard indexes with different projections to exist. It is therefore legal to do this:
... but illegal to do the following, even though the indexes should be functionally identical to the above:
More significantly, the former syntax is limited to inclusion of a single path; permitting the latter would be far more powerful in allowing the user to create separate wildcard indexes to index different sections of their dataset. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 22/Nov/21 ] |
|
Author: {'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}Message:
|