[SERVER-11479] aggregate and collMod commands should accept maxTimeMS option Created: 30/Oct/13  Updated: 02/Aug/18  Resolved: 01/Nov/13

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Gregory McKeon (Inactive)
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:

 Description   

Running both commands on mongod gives following errors.

> db.runCommand({ aggregate : "foo", pipeline : [{ $match: { i: 0 } }], maxTimeMS: 1000 })
{ "ok" : 0, "errmsg" : "unrecognized field 'maxTimeMS'" }
 
> db.runCommand({collMod: "foo", usePowerOf2Sizes : false, maxTimeMS: 1000 });
{ "ok" : 0, "errmsg" : "unknown option to collMod: maxTimeMS" }



 Comments   
Comment by auto [ 01/Nov/13 ]

Author:

{u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}

Message: SERVER-11479 Style for string comparison
Branch: master
https://github.com/mongodb/mongo/commit/2171249d6e32178e13e712c53b166bae57b525da

Comment by auto [ 01/Nov/13 ]

Author:

{u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}

Message: SERVER-11479 aggregate/collMod should not reject maxTimeMS option
Branch: master
https://github.com/mongodb/mongo/commit/defb7631265b55f15c001393858f30e0bd388805

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