[SERVER-78949] Consider folding atClusterTime into readConcern object in TransactionRouter::SharedTransactionOptions Created: 13/Jul/23  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-79763 Default read concern setting is not b... Backlog
related to SERVER-79766 TransactionRouter ignores atClusterTi... Backlog
Assigned Teams:
Cluster Scalability
Participants:

 Description   

https://github.com/mongodb/mongo/blob/8837a2dfe2bf2859e481fa18ca22cda36a44f1ca/src/mongo/s/transaction_router.h#L114

The separate atClusterTime member was needed because the read concern setting was immutable before v5.0.


Generated at Thu Feb 08 06:39:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.