Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-3217

Allow manually specifying maxTimeMS on commands when the auto-calculated value is omitted

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.15.1
    • Affects Version/s: 1.15.0
    • Component/s: None
    • None
    • Go Drivers
    • Not Needed
    • 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?

      Context

      Starting with Go Driver v1.15.0 (GODRIVER-3172), maxTimeMS is now sent on all commands when timeoutMS is set (i.e. a client-level timeout), including when a Context with deadline is used (i.e. an operation-level timeout), with two exceptions: Find and Aggregate operations. To align with the proposed behavior in DRIVERS-2722, we omit maxTimeMS on operations that return a cursor. However, we don't support timeoutMode yet, so that leaves no way to set a maxTimeMS (i.e. a server-side timeout) on Find and Aggregate ops. For those two commands, continue to honor the deprecated MaxTime option, allowing users to re-enable maxTimeMS.

      Definition of done

      What must be done to consider the task complete?

      Pitfalls

      What should the implementer watch out for? What are the risks?

            Assignee:
            matt.dale@mongodb.com Matt Dale
            Reporter:
            matt.dale@mongodb.com Matt Dale
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: