[SERVER-72462] Extend wildcardProjection to support compound wildcard indexes Created: 03/Jan/23 Updated: 29/Oct/23 Resolved: 19/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ruoxin Xu | Assignee: | Alexander Ignatyev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | M1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QO 2023-01-23 |
| Participants: |
| Description |
|
This should allow specifying ‘wildcardProjection’ when creating a compound wildcard index, which includes: 1. validating the ‘wildcardProjection’ option (e.g. wildcardProjection should only ever be specified if the wildcard field is “$**” and should exclude all overlapping fields) 2. Extend support in which cases ‘wildcardProjection’ is used: a) The Index indexability/discriminators encoding for Plan cache keys b) Planner params fill-out process. |
| Comments |
| Comment by Githook User [ 19/Jan/23 ] |
|
Author: {'name': 'Alexander Ignatyev', 'email': 'alexander.ignatyev@mongodb.com', 'username': 'aligusnet'}Message: |