[SERVER-3282] notablescan option with configuration server Created: 17/Jun/11  Updated: 06/Dec/22  Resolved: 21/Dec/21

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

Type: Improvement Priority: Trivial - P5
Reporter: Mr Pause Assignee: Backlog - Query Execution
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Amazon EC2 small instance
Linux 2.6.35.11-83.9.amzn1.i686 #1 SMP Sat Feb 19 23:41:56 UTC 2011 i686 i686 i386 GNU/Linux


Issue Links:
Related
Assigned Teams:
Query Execution
Participants:

 Description   

notablescan option is allowed for configuration servers even if it cant function properly without table scans



 Comments   
Comment by Joe Kanaan [ 21/Dec/21 ]

notablescan is a long standing user option that people use. We are closing as won't do.

Comment by Kaloian Manassiev [ 17/Dec/21 ]

We will not spend time forbidding it on the config server. Passing this ticket to Query to decide whether we should just throw out the option given that we have $explain stage, etc.

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