As part of enabling the usage of $lookup against foreign sharded collections while in a transaction we want to add a test that verifies the behaviour is the expected.
Note that this should mostly concern snapshot isolation transactions since multi-document transactions that are done with any other readConcern have non-trivial semantics to reason about.
- depends on
-
SERVER-84470 Allow $lookup to target an unsplittable collection on a primary shard within a multi-document transaction
- Closed
-
SERVER-89413 Fix deadlock in TransactionRouter
- Closed
-
SERVER-89650 Aggregations can retry non-idempotent operations that use cursors on certain failures
- Closed
-
SERVER-89893 Change executor used by _flushReshardingStateChange from arbitrary to fixed
- Closed