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

give change stream a timeout option to override the client's timeout

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Do
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: CSOT
    • None
    • None
    • Go Drivers
    • 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

      In normal project,most of the operate to database is CRUD,so user can set a timeout on the mongo's client to make sure it will not block too much time.

      But if the user needs to use the change stream at the same time,the change stream will be effected by the client's timeout.However,if user want to use the change stream,the user usually don't want the stream to be disconnected.

      Current way to solve this problem is to create 2 clients,one has no timeout,one has timeout.But this is so ugly.

      If we can have an option on the change stream to override the client's timeout,it will be fine.

       

            Assignee:
            preston.vasquez@mongodb.com Preston Vasquez
            Reporter:
            chenjie199234@gmail.com 杰 陈
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None