[SERVER-33838] Replace setStashedCursor and hasStashedCursor with transaction state Created: 12/Mar/18 Updated: 27/Oct/23 Resolved: 24/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Sprint: | Repl 2018-04-23 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Multi-statement transaction shares the same resource stashing logic in sessions with local snapshot read. |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 23/Mar/18 ] |
|
This may not be important now that we are removing support for snapshot reads outside of transactions. For example, we could also remove setStashedCursor() as part of |