[SERVER-64645] Add a query knob to disable covered scans of null range Created: 18/Mar/22 Updated: 20/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
The fix for SERVER-23229 is really to update the index to distinguish the two values. Until then a fix would come with performance ramifications. As a mitigation (and to help some of our test infrastructure), we could add a query knob to disable the covered index scans when they lead to incorrect behavior. |
| Comments |
| Comment by Charlie Swanson [ 02/Dec/22 ] |
|
I'm moving this back to the backlog state since I haven't gotten around to it at the bottom of my TODO list for quite some time. I've had no reason to prioritize it really since the BF it's linked to is pretty quiet of late. If someone finds a reason to do this later, don't hesitate to reach out! Still seems like a reasonable idea. |