[DOCS-13227] Add wildcardProjection warning Created: 15/Nov/19 Updated: 30/Oct/23 Resolved: 17/Jan/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Danny Hatcher (Inactive) | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | docs-4.2-wildcard | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 42 weeks, 6 days ago | ||||||||
| Epic Link: | DOCS: 4.2 Server/Tools | ||||||||
| Description |
DescriptionThe wildcard indexes documentation explains how to include or exclude specific fields via wildcardProjection. As part of our core projection semantics we are unable to selectively exclude subfields when we include a top-level field and this seems like it would be possible according to our current docs. We should add a warning to the wildcard indexes page specifically mentioning that this is impossible. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Jess Mokrzecki [ 14/Apr/22 ] |
|
Fix Version updated for upstream SERVER-44558: |
| Comment by Githook User [ 17/Jan/20 ] |
|
Author: {'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com'}Message: |
| Comment by Ravind Kumar (Inactive) [ 16/Jan/20 ] |