[SERVER-34366] Transactions shell helpers shouldn't attach readConcern to any operation but the first in a transaction Created: 06/Apr/18  Updated: 29/Oct/23  Resolved: 14/Apr/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-34348 Test that transactions play well with... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-04-23
Participants:

 Description   

When running transactions within a causally consistent session in the shell, all operations in the transaction get an afterClusterTime readConcern attached to them, which will cause all operations after the first to error with InvalidOptions since readConcern is only allowed on the first operation in the transaction



 Comments   
Comment by Githook User [ 14/Apr/18 ]

Author:

{'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou', 'username': 'visualzhou'}

Message: SERVER-34366 Shell api supports causal consistency.
Branch: master
https://github.com/mongodb/mongo/commit/3538f6e2174056f57e05928790e6229ced39e691

Generated at Thu Feb 08 04:36:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.