[SERVER-18332] Command form of getMore should support maxTimeMs Created: 05/May/15  Updated: 11/May/15  Resolved: 08/May/15

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

Type: Improvement Priority: Major - P3
Reporter: Andy Schwerin Assignee: David Storch
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-18184 Add awaitData support to getMore command Closed
Participants:

 Description   

When present on the getMore, a specified maxTimeMs argument should override the value on the cursor. This will allow maxTimeMs to be used in place of the "wait data timeout", which is currently fixed at 1 second, and is compatible with the existing cursor max time behavior.

When maxTimeMs is set on the getMore command, the value stored in the cursor itself should be ignored, and not updated.



 Comments   
Comment by David Storch [ 08/May/15 ]

Although not exactly a duplicate, this work will be done as part of SERVER-18184.

Comment by Eric Milkie [ 05/May/15 ]

Never mind, I think you still need it to tell the query system to wait instead of returning when there is no data. You need maxTimeMs to configure the waiting.
So if someone uses maxTimeMs on a getmore command for a cursor which was not flagged as AwaitData, it will still need to override the existing maxTimeMs in the cursor, if it was used in the find command.

Comment by Eric Milkie [ 05/May/15 ]

I think this means we can also remove support for the "AwaitData" query option in the new find command.

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