[SERVER-39866] Make cluster aggregate use MultiStatementTransactionRequestsSender rather than using ShardRemote and manually calling attachTxnFields Created: 27/Feb/19  Updated: 29/Oct/23  Resolved: 01/Mar/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.9

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: ShardedTxn:ReadOnly
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-03-11
Participants:

 Description   

This is a prerequisite to skipping two-phase commit for read-only transactions, since we would like to have one place where the router needs to process the new 'readOnly' field in a participant shard's response for a transaction statement, and all other egress paths through mongos that can be run in a transaction use the MultiStatementTransactionRequestsSender.



 Comments   
Comment by Githook User [ 01/Mar/19 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-39866 Make cluster aggregate use MultiStatementTransactionRequestsSender rather than using ShardRemote and manually calling attachTxnFields
Branch: master
https://github.com/mongodb/mongo/commit/e5ee880b03e4be83a56004d9e9d43852a6960eec

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