[SERVER-36793] Ban $in queries for allPaths indices which contain unsupported values Created: 21/Aug/18 Updated: 10/Sep/18 Resolved: 10/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Ian Boros |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Query 2018-09-24 | ||||||||
| Participants: | |||||||||
| Description |
|
Example:
This query will attempt to use an allPaths index. We should make sure that it doesn't. |
| Comments |
| Comment by Ian Boros [ 10/Sep/18 ] |
|
I plan on doing this work under |
| Comment by David Storch [ 21/Aug/18 ] |
|
If possible, we should partially index an $in, such as the one above, rather than failing to use the index for the $in entirely. This would likely involve "detaching" any predicates that are not compatible with the index from the $in MatchExpression node, and generating an $or MatchExpression node internally. |