[SERVER-70597] QueryPlannerAccess::processIndexScans fails when MatchExpression is not optimized Created: 14/Oct/22 Updated: 29/Oct/23 Resolved: 17/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | David Percy |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Linked BF Score: | 13 | ||||
| Description |
|
It looks like when the 'disableMatchExpressionOptimization' failpoint is set, QueryPlannerAccess can do an incorrect static_cast. We should fix this to prevent it from happening in the optimization fuzzer. We also might as well use checked_cast to make diagnosis easier. |
| Comments |
| Comment by Githook User [ 17/Jan/23 ] |
|
Author: {'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}Message: |
| Comment by Githook User [ 30/Nov/22 ] |
|
Author: {'name': 'David Percy', 'email': 'david.percy@mongodb.com', 'username': 'dpercy'}Message: When tests use disableMatchExpressionOptimization (an internal-only |