-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
None
-
Query
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The create command should not accept the maxTimeMS option, because we do not check for interrupt within its execution. However, create could not reject maxTimeMS in 3.4, because a 3.2 mongos attaches a maxTimeMS when creating the changelog and actionlog collections on the config servers. In 3.6, we should be able to disallow maxTimeMS for create.
- is related to
-
SERVER-26450 Whitelist maxTimeMS option to create command
-
- Closed
-