[SERVER-2222] notablescan mode neglects to fail some table scan queries Created: 14/Dec/10 Updated: 03/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
These are just the cases I've run into, possibly there are more: t.find( {} );
t.find( ... );
t.count( {a:1});
Maybe we want to allow some of these cases, but if so we should document that fact. |
| Comments |
| Comment by Dwight Merriman [ 14/Feb/12 ] | |||
|
commit 338ef8c94b9677242a52e8855eecbfc449c9da76 slight improvement in noTableScan code | |||
| Comment by Aaron Staple [ 23/Jan/12 ] | |||
|
An issue with notablescan namespace whitelist matching
The pattern matching should be more precise to prevent table scans from sneaking through on namespaces like 'my_local.foo'. Also not clear that all local namespaces should be in the whitelist. | |||
| Comment by Colin Howe [ 19/Nov/11 ] | |||
As a user of the table scan exception functionality my initial thought was that this case is the correct behaviour. However, if there were to be any rows than this would be a table scan. Advance warning of this on an empty table would be useful! |