[SERVER-73387] Rule out compound wildcard indexes in query planning Created: 27/Jan/23 Updated: 29/Oct/23 Resolved: 27/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: | Ruoxin Xu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | M2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | QO 2023-02-06 | ||||
| Participants: | |||||
| Linked BF Score: | 160 | ||||
| Description |
|
After enabling the creation of Compound wildcard indexes, we should still ban compound wildcard indexes for any query because there're still some existing restrictions/invariants on CWI. Consider imposing index checks before using CWI in query planning. |
| Comments |
| Comment by Githook User [ 27/Jan/23 ] |
|
Author: {'name': 'Ruoxin Xu', 'email': 'ruoxin.xu@mongodb.com', 'username': 'RuoxinXu'}Message: |