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