[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: |
| Comment by Tess Avitabile (Inactive) [ 28/Feb/18 ] |
|
Yes, I agree it is a requirement for |
| 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 ] |