Error if MaxAwaitTime will cause client-side timeout

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      When users set MaxAwaitTime and Timeout , getMore s from change streams or cursors can currently append multiple maxTimeMS values. Remove maxTimeMS appension logic in batch cursor. Modify calculateMaxTimeMS to respect MaxTime for getMore unless Timeout is set and deadline will be exceeded. If deadline will be exceeded, throw ErrDeadlineWouldBeExceeded with relevant information.

            Assignee:
            Unassigned
            Reporter:
            Benji Rewis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: