[SERVER-3342] utilize index for full collection scan in some cases Created: 27/Jun/11  Updated: 06/Dec/22  Resolved: 18/Apr/16

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-20066 Query planner should consider index s... Closed
Related
is related to SERVER-2140 query optimizer should be able to pic... Closed
Assigned Teams:
Query
Operating System: ALL
Participants:

 Description   

described in an email to me as:

{ x : <anything> }

including not, $or, regex, whatever, sometimes just scanning the whole index would be better than a table scan. i assume query optimizer is not testing that plan at the moment (with minkey and maxkey the full range)? should we do that?



 Comments   
Comment by David Storch [ 18/Apr/16 ]

Closing as a duplicate of SERVER-20066, since the newer ticket has a more useful description.

Generated at Thu Feb 08 03:02:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.