-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Core, Sessions, Transactions
In our command construction, we are automatically adding a readConcern.afterClusterTime to every command that has a session. The Causal Consistency spec only says to add afterClusterTime to read commands, and explicitly says to not add it to runCommand-like behavior.
While this will likely not break anything in the server, it does cause some errors when attempting to comply with spec tests that assert whether or not a readConcern is present