We have a uassert that should prevent individual transaction statements from specifying their own readConcern. However, we wait for read concern before calling runCommandImpl, which is where our uassert executes.
As a result, if we specify a readConcern for a statement following the first statement in the transaction, we will fail the uassert, but not until after actually waiting for the read concern.
- related to
-
SERVER-47508 opCtx->inMultiDocumentTransaction() is set to true for test case run "outside" of a transaction
-
- Closed
-
-
SERVER-47861 Investigate consolidation of readConcern validation
-
- Closed
-