[SERVER-38051] Add warning/check mechanism to explain() output for old indexes and multikey Created: 09/Nov/18 Updated: 06/Dec/22 Resolved: 05/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Nic Cottrell | Assignee: | Backlog - Query Execution |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
I've seen many cases of updating from 3.2 and hitting It would be great if explain() could include some heuristic checks (similar to startupWarnings in mongod) which look for common problems are report them in the output as warnings. Something like "Winning index needs to be rebuilt to benefit from |