[SERVER-41137] abortTransaction on mongos does not propagate user's writeConcern Created: 14/May/19 Updated: 29/Oct/23 Resolved: 04/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.14, 4.2.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Alexander Taskov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Sharding 2019-06-03, Sharding 2019-06-17 | ||||
| Participants: | |||||
| Description |
|
It's a one-line change on the server, but this ticket should add testing that the user's writeConcern is propagated. |
| Comments |
| Comment by Githook User [ 02/Jul/19 ] |
|
Author: {'name': 'Alex Taskov', 'username': 'alextaskov', 'email': 'alex.taskov@mongodb.com'}Message: (cherry picked from commit f75aa0003333eefd1e1c56039bd1d44c44fb3620) |
| Comment by Githook User [ 04/Jun/19 ] |
|
Author: {'name': 'Alex Taskov', 'email': 'alex.taskov@mongodb.com', 'username': 'alextaskov'}Message: |