-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Repl 2021-10-18
If a stage doesn't run for certain read concerns and that stage is run in a transaction, we don't check for whether the readconcern/stage combo is legal. It looks like the check should be here, but is skipped for the aggregate command.
- related to
-
SERVER-60038 Ban setWindowFields in transaction with read concern snapshot
- Closed