[SERVER-64366] Investigate if we can support $nin queries better Created: 09/Mar/22 Updated: 24/Jan/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
Some of the demo queries we've seen that we want to use the columnar index include odd predicates like {$nin: []} or {$nin: [null]}. The first should be always true. The second may be able to be pushed down? Worth investigating and testing. |
| Comments |
| Comment by Irina Yatsenko (Inactive) [ 28/Dec/22 ] |
|
We are pushing down $not of supported predicates now, but it doesn't help {$nin: [null]} or {$ne: null} because {$eq: null} and {$in: [null]} aren't supported. |