Command form of getMore should support maxTimeMs

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              David Storch
              Reporter:
              Andy Schwerin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: