[SERVER-34410] Test reads in transactions that require more than one batch Created: 10/Apr/18 Updated: 03/May/18 Resolved: 03/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Repl 2018-05-21 | ||||||||
| Participants: | |||||||||
| Description |
|
We should make sure we're testing getMores within transactions. |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 03/May/18 ] |
|
I agree with james.wahlin. In particular, we haveĀ snapshot_reads.js, which tests read commands that require three batches. |
| Comment by James Wahlin [ 10/Apr/18 ] |
|
Please note that we are converting the former snapshot reads tests over to use multi-statement transactions where it makes sense. This work is being handled by |