You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/** The time in milliseconds to attempt a connection before timing out. */
154
154
connectTimeoutMS?: number;
155
-
/** The time in milliseconds to attempt a send or receive on a socket before the attempt times out. */
155
+
/**
156
+
* The time in milliseconds to attempt a send or receive on a socket before the attempt times out.
157
+
* @deprecated Will be removed in the next major version. Please use timeoutMS instead
158
+
*/
156
159
socketTimeoutMS?: number;
157
160
/** An array or comma-delimited string of compressors to enable network compression for communication between this client and a mongod/mongos instance. */
/** Return the query as cursor, on 2.6 \> it returns as a real cursor on pre 2.6 it returns as an emulated cursor. */
28
28
cursor?: Document;
29
-
/** specifies a cumulative time limit in milliseconds for processing operations on the cursor. MongoDB interrupts the operation at the earliest following interrupt point. */
29
+
/**
30
+
* Specifies a cumulative time limit in milliseconds for processing operations on the cursor. MongoDB interrupts the operation at the earliest following interrupt point.
31
+
* @deprecated Will be removed in the next major version. Please use timeoutMS instead.
32
+
*/
30
33
maxTimeMS?: number;
31
34
/** The maximum amount of time for the server to wait on new documents to satisfy a tailable cursor query. */
// if the write concern was specified with wTimeoutMS, then we set both wtimeoutMS and wTimeoutMS, guaranteeing at least two keys, so if we have more than two keys, then we can automatically assume that we should add the write concern to the command. If it has 2 or fewer keys, we need to check that those keys aren't the wtimeoutMS or wTimeoutMS options before we add the write concern to the command
0 commit comments