[DOCS-11035] Outdated statement in "Write Concern for Replica Sets" docs Created: 17/Nov/17  Updated: 29/Oct/23  Resolved: 12/Dec/17

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 3.6.0-rc5

Type: Bug Priority: Major - P3
Reporter: James Wahlin Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: writeconcern
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.mongodb.com/master/core/replica-set-write-concern/


Issue Links:
Related
is related to DOCS-10736 Docs for SERVER-28918: Make CRUD writ... Closed
Participants:
Days since reply: 6 years, 9 weeks, 1 day ago
Story Points: 0.1

 Description   

RE: https://docs.mongodb.com/master/core/replica-set-write-concern/

This page starts of by stating:

From the perspective of a client application, whether a MongoDB instance is running as a single server (i.e. “standalone”) or a replica set is transparent. However, replica sets offer some configuration options for write.

With the introduction of change streams in 3.6 this is no longer the case and doesn't really add much to a readers understanding of write concern.



 Comments   
Comment by Kay Kim (Inactive) [ 12/Dec/17 ]

forgot to update the status a while back.

https://github.com/mongodb/docs/commit/b066f96609ba114596b21e20bfad006cd51e0e2f

Comment by Kay Kim (Inactive) [ 17/Nov/17 ]

Since I need to update the distributed read and write pages, will clean up.

Comment by Jeffrey Allen [ 17/Nov/17 ]

Should be a quick fix as we can just remove the sentence mentioned. I agree that with the 3.6 changes it no longer serves any positive purpose and will likely confuse users.

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