[SERVER-33047] Error if write concern provided as part of a write of a multi-statement transaction Created: 31/Jan/18 Updated: 06/Dec/22 Resolved: 28/Feb/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: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
The 'commitTransaction' and 'abortTransaction' commands are the only part of a multi-statement transaction that are allowed to specify a writeConcern. Individual writes as part of an ongoing transaction should error if they provide a writeConcern. |