[SERVER-56868] Fix semantics for write concern provenance when implicit default is used Created: 11/May/21  Updated: 29/Oct/23  Resolved: 25/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc1, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Huayu Ouyang
Resolution: Fixed Votes: 0
Labels: post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-55702 Update 'defaultRWConcern' section of ... Closed
Related
related to SERVER-56861 Update semantics for server status's ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Repl 2021-05-31
Participants:

 Description   

We set the write concern provenance to be customDefault even when using the implicit default because of this line. customeDefaultWasApplied should be set based on the DefaultWriteConcernSource. We should update this in strategy.cpp similarly.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 25/May/21 ]

Author:

{'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}

Message: SERVER-56868 Fix semantics for write concern provenance when implicit default is used

(cherry picked from commit c36d0bfc237c36c34518771864a49dcf78527e9b)
Branch: v5.0
https://github.com/mongodb/mongo/commit/e794187dd9a5050a7b23bb0b41f701631e738c81

Comment by Githook User [ 25/May/21 ]

Author:

{'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}

Message: SERVER-56868 Fix semantics for write concern provenance when implicit default is used
Branch: master
https://github.com/mongodb/mongo/commit/c36d0bfc237c36c34518771864a49dcf78527e9b

Generated at Thu Feb 08 05:40:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.