[SERVER-86201] Cluster upserts performed through the ShardServerProcessInterface should use the operation context to configure their write concern Created: 05/Feb/24  Updated: 06/Feb/24  Resolved: 06/Feb/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 7.0.5, 8.0.0-rc0, 7.3.0-rc1
Fix Version/s: 8.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-80363 server default writeConcern is not ho... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.3, v7.0
Sprint: CAR Team 2024-02-05
Participants:

 Description   

The ShardsServerProcessInterface flavour of the MPI API implements the insert and update methods by using BatchedCommandRequests that get dispatched through cluster::write(). The semantics of such a method have been recently modified by SERVER-80363, so that the the opCtx (instead of the related BatchedCommandRequest setter) needs to be used now to configure the write concern of the remote command being dispatched.



 Comments   
Comment by Githook User [ 06/Feb/24 ]

Author:

{'name': 'ppolato', 'email': '82828243+ppolato@users.noreply.github.com', 'username': 'ppolato'}

Message: SERVER-86201 Fix writeConcern configuration in ShardServerProcessInterface::insert/update() (#18687)

GitOrigin-RevId: dbb9c9d1ace105003f844286b299c1c63fd807ef
Branch: master
https://github.com/mongodb/mongo/commit/4dfa65eab841fa816ac96072fa3cf78509abb4a2

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