[SERVER-2217] fix notablescan Created: 14/Dec/10  Updated: 12/Jul/16  Resolved: 14/Dec/10

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

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Comments   
Comment by auto [ 14/Dec/10 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-2217 queryoptimizer handle properly when notablescan exception is generated in queryop init
https://github.com/mongodb/mongo/commit/9c14510e648868e5e544599a17d7b0f7006d9907

Comment by auto [ 14/Dec/10 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-2217 fix parsing of notablescan command line option
https://github.com/mongodb/mongo/commit/d2092adc167ef848dec73708a393e664c49d8e0a

Comment by Aaron Staple [ 14/Dec/10 ]

There is a problem with command line parsing, and another problem with handling plans that err out in init.

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