[SERVER-34340] Transaction starting with getMore() is not able to take snapshot readConcern Created: 05/Apr/18 Updated: 27/Oct/23 Resolved: 05/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | Needs Triage |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | session.startTransaction({readConcern: {level: "snapshot"}}) ) |
||||||||
| Participants: | |||||||||
| Description |
|
We always attach the first statement of the transaction with the readConcern. Imagine a case we want to start a transaction with a getMore() command. The server will give an error "Command does not support read concern snapshot". Please feel free to close this if it is not a concern. |
| Comments |
| Comment by Xiangyu Yao (Inactive) [ 05/Apr/18 ] |
|
If that's the case, I'm okay with closing this ticket. |
| Comment by Siyuan Zhou [ 05/Apr/18 ] |
|
GetMore should never be the first command in a transaction, otherwise it's a bug in driver. xiangyu.yao, what is your expected behavior? |