[SERVER-33531] Read concern should be stashed with transaction resources Created: 27/Feb/18  Updated: 29/Oct/23  Resolved: 07/Mar/18

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 3.7.3

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

Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-03-12
Participants:

 Description   

For multi-statement transactions, we must stash the readConcern with transaction resources. The readConcern is specified on the first statement of a multi-statement transaction, but it applies to all subsequent statements in the multi-statement transaction and is necessary for selecting the correct yield policy.



 Comments   
Comment by Githook User [ 07/Mar/18 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-33531 Read concern should be stashed with transaction resources
Branch: master
https://github.com/mongodb/mongo/commit/0a965b0b212e6c0487bda8352dfcda3381e0e2b7

Comment by Tess Avitabile (Inactive) [ 28/Feb/18 ]

Yes, I agree it is a requirement for SERVER-33215. spencer was interested in separating out this work to allow siyuan.zhou to focus on that ticket and was curious if we had the bandwidth to pick it up.

Comment by Eric Milkie [ 28/Feb/18 ]

I would presume that anyone adding stashing to a particular command should include this functionality described in this ticket (otherwise, the code change would be functionally incorrect).

Comment by Tess Avitabile (Inactive) [ 27/Feb/18 ]

milkie, spencer, which project should pick up this work?

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