[SERVER-79820] Fix ord.js so it ensures an ixscan plan is used Created: 08/Aug/23 Updated: 29/Oct/23 Resolved: 10/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Hana Pearlman | Assignee: | Hana Pearlman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 59 | ||||
| Description |
|
The ord.js file tests that "dropping indexes required by an indexed $or causes the query to fail cleanly". But, with CQF, we may choose a collscan for the query, since neither of the predicates are particularly selective. This test relies on the query optimizer choosing an ixscan plan, so it should hint an index or make the predicates more selective to ensure this is true. Note that this only affects CQF M4. |
| Comments |
| Comment by Githook User [ 10/Aug/23 ] |
|
Author: {'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}Message: |