[SERVER-77188] [CQF] Test that Bonsai uses the multikeyness info of all indexes when a persistent hint or index filter is present Created: 16/May/23 Updated: 23/May/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hana Pearlman | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | starter, testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
After This ticket is to add tests to make sure this is true for persistent hints and index filters too. |
| Comments |
| Comment by David Percy [ 22/May/23 ] |
|
Just to clarify, when you say "hidden indexes" I think you mean generally things like hints, persistent hints, index filters? Because there is a specific feature called "hidden indexes": https://www.mongodb.com/docs/v6.0/core/index-hidden/. And I think we don't want to use the multikeyness info of indexes hidden this way. People mark indexes hidden to find out what the consequences of dropping the index would be, while still being able to undo easily. So as much as possible, the optimizer should pretend these hidden indexes don't exist. |