[SERVER-33983] Add support for transactions in readConcern passthrough suites Created: 19/Mar/18 Updated: 29/Oct/23 Resolved: 21/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | William Schultz (Inactive) | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:Testing, todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Sharding 2018-12-03, Sharding 2018-12-17, Sharding 2018-12-31 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
We should run a passthrough suite that supports starting transactions with various supported readConcern levels. One example would be the read_concern_majority_passthrough suite. A readConcern argument is only supported on the first command of a transaction, so we may need to make changes in set_read_and_write_concerns.js to make this work correctly. |
| Comments |
| Comment by Githook User [ 06/Feb/20 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |
| Comment by Githook User [ 20/Dec/18 ] |
|
Author: {'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}Message: |
| Comment by Githook User [ 20/Dec/18 ] |
|
Author: {'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}Message: |
| Comment by Gregory McKeon (Inactive) [ 19/Jun/18 ] |
|
Passing this to sharding since we think their changes to readConcerns in transactions will cause this testing to be more important. |