-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Query Execution
-
None
-
Fully Compatible
-
Query Execution 2021-05-03
We should enable the following suites against the SBE build variant, all of which run tests in jstests/core/ against a sharded test fixture:
- sharding_jscore_passthrough
- sharded_causally_consistent_jscore_passthrough
- sharded_collections_jscore_passthrough
- multi_shard_multi_stmt_txn_jscore_passthrough
- multi_shard_multi_stmt_txn_kill_primary_jscore_passthrough
- multi_shard_multi_stmt_txn_stepdown_primary_jscore_passthrough
- multi_stmt_txn_jscore_passthrough_with_migration
- sharding_jscore_op_query_passthrough
- sharding_jscore_passthrough_wire_ops
- sharding_update_v1_oplog_jscore_passthrough
We should link this as dependent on tickets that currently block our ability to enable these suites with SBE.
- depends on
-
SERVER-56073 [SBE] Wrong number of results in jstests/core/idhack.js under multi_shard_multi_stmt_txn_jscore_passthrough
- Closed
-
SERVER-56076 [SBE] jstests/core/sbe/sbe_cmd.js should be tagged such that it does not run against mongos
- Closed
-
SERVER-56079 [SBE] jstests/core/index_bounds_static_limit.js fails in sharded jscore passthroughs with SBE on
- Closed
-
SERVER-56143 [sbe][multi_shard_multi_stmt_txn_jscore_passthrough] Tests fail because of incorrect nReturned stat in executionStats
- Closed