[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:

  • Configuring the OP_MSG to not generate a response
  • Not returning the result of the write


 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
configured write concern for all decisions, including

  • whether to expect a response to the wire message
  • whether to return an acknowledged bulk write result
  • whether the write is retryable

JAVA-3282
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/8399286e8919b3af9361ab27cfbf6d7a14ee479b

Generated at Thu Feb 08 08:59:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.