[SERVER-1187] Queries should return information if $maxScan was reached Created: 02/Jun/10 Updated: 07/Apr/23 Resolved: 14/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Thomas Zehetner | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 8 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
Sometimes it's useful to know if $maxScan was reached during query execution (for example if you want to inform your users about it). Therefore there should be a way to know if query execution reached $maxScan. |
| Comments |
| Comment by David Storch [ 14/Feb/18 ] |
|
The maxScan feature is being deprecated (see |
| Comment by Drew Perttula [ 17/Apr/12 ] |
|
I have a case where I'd actually like to know the record that was reached at maxScan, so I can plan a followup query. Case 1: Case 2: |
| Comment by Kevin Lacker [ 23/Jan/12 ] |
|
This would definitely be helpful. For safety I would like to prevent any engineer working on the codebase from introducing a query that hits maxScan, so I want to add code in our db wrapper layer that throws an error whenever that happens. |
| Comment by Simon Jakubowski [ 26/Oct/11 ] |
|
That would be a very helpful feature! |