-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 7.0.0-rc0
-
Component/s: None
-
None
-
Query Integration
-
ALL
-
v8.0, v7.3
-
-
QI 2023-04-17
-
162
runCommandWithApiStrict used in the sharding_api_strict_passthrough suite does not always run find commands with api strict, but it always runs getMore commands with api strict. This will cause failures on any getMore commands for find commands that aren't run with api strict.
This is especially a problem because the teardown of the replsettest (used by the shardingtest for config servers) runs a find command with noCursorTimeout for checking the oplog. This means that if any test creates an oplog big enough to require calling getMore to traverse the oplog, the teardown of the test will fail with the following error:
"API parameter mismatch: getMore used params { apiVersion: \"1\", apiStrict: true }, the cursor-creating command used {}"
- depends on
-
SERVER-76229 Allow find() test shell helper to accept any parameter
- Backlog
- is related to
-
SERVER-75755 Remove auth.js and transactions_writes_not_retryable.js from sharding_api_strict_passthrough
- Closed