[SERVER-10845] Specifying notablescan in connection string / in single query Created: 23/Sep/13  Updated: 09/Jul/16  Resolved: 23/Sep/13

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

Type: New Feature Priority: Major - P3
Reporter: Stephan Ryer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: indexes, notablescan, query
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-1143 Allow --notablescan to be specified p... Backlog
Backwards Compatibility: Fully Compatible
Participants:

 Description   

As for now it seems, that notablescan is defined at server level only. I would like this to be a parameter that could be defined at a lower level e.g. in the connection-string.

This would allow one to ensure, that all queries done from production code uses indexes and still I will be able to do ad-hoc queries on my production data in debugging scenarios.

This feature may naturally be overruled if notablescan is ON at server level.

In case notablescan could be defined in the query string, the only change needed to the documentation is instruction hereof.



 Comments   
Comment by Stephan Ryer [ 23/Sep/13 ]

Sorry, duplicate of this: SERVER-1143

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