[JAVA-3282] Unacknowledged write concern set on collection incorrectly applied when in a transaction Created: 02/May/19 Updated: 28/Oct/23 Resolved: 03/May/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Transaction Management |
| Affects Version/s: | None |
| Fix Version/s: | 3.11.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The drivers transactions specification requires that any write concern configured at the collection level is ignored when in a transaction. For the most part, the driver does this, but in the case where that configured write concern is unacknowledged, that write concern is incorrectly applied to make several wrong decisions, including:
|
| Comments |
| Comment by Githook User [ 03/May/19 ] |
|
Author: {'email': 'jeff.yemin@10gen.com', 'name': 'Jeff Yemin', 'username': 'jyemin'}Message: Apply the default write concern when in a transaction When in a transaction, an insert, update or delete now ignores the
|