Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
None
-
Minor Change
-
v5.0
-
Elastic 2021-05-24
Description
We decided not to use the requireApiVersion parameter in Atlas, so let's consider removing it. Update: we decided not to remove it, but to make it test-only.
Attachments
Issue Links
- is documented by
-
DOCS-14470 Investigate changes in SERVER-56925: Remove requireApiVersion server parameter?
-
- Closed
-
- is related to
-
DRIVERS-1619 Provide informative handshake error message when Versioned API requested from downlevel server
-
- Backlog
-
-
SERVER-50784 Must disable requireApiVersion after all fuzz tests
-
- Closed
-
-
SERVER-52612 Can't use getMore or transaction-continuing commands when requireApiVersion parameter is true
-
- Closed
-
-
SERVER-54122 Fix fuzzer_tests bug of setting requireApiVersion to true and not cleaning it.
-
- Closed
-
- related to
-
SERVER-50533 Avoid setting requireApiVersion parameter in jstestfuzz
-
- Closed
-
-
SERVER-53499 dropRole fails when requireApiVersion=1
-
- Closed
-
-
SERVER-53555 Performance regression for dropping/creating collections with requireApiVersion and majority write concern
-
- Closed
-
-
DOCS-13824 Investigate changes in SERVER-49887: requireApiVersion startup parameter
-
- Closed
-
-
DOCS-14240 Investigate changes in SERVER-53934: Refuse to start shards and config servers with setParameter requireApiVersion=true
-
- Closed
-
-
SERVER-49887 requireApiVersion startup parameter
-
- Closed
-