[SERVER-29987] Make all non-write operations take readConcern Created: 05/Jul/17  Updated: 30/Oct/23  Resolved: 15/Aug/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.12

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: PM-221
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-30463 add support for readConcern to explain Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-08-21
Participants:

 Description   

With causal consistency going as default and therefore with readConcern with afterClusterTime being added to every command by shell or driver it becomes important to always ensure that the readConcern requirement is met.
as
This task will
1. change the name of supportsReadConcern to supportsReadConcernMajority to reflect its semantics
2. change mongo shell to add the readConcern to all commands that do not write.



 Comments   
Comment by Githook User [ 15/Aug/17 ]

Author:

{'username': 'mikety', 'email': 'misha@mongodb.com', 'name': 'Misha Tyulenev'}

Message: SERVER-29987 pass afterClusterTime to all commands
Branch: master
https://github.com/mongodb/mongo/commit/eacef2db99841b1a88837f0e10d1c8726656dc0f

Comment by Misha Tyulenev [ 06/Jul/17 ]

The "pure" commands can skip the wait - its an optimization. But for the simplicity of driver's implementation I suggest to always validate the read concern even if its not being used.

Comment by Eric Milkie [ 06/Jul/17 ]

Some commands make no reads or writes (or ever acquire a database lock). Must we make them support read concern? Isn't that confusing?

Generated at Thu Feb 08 04:22:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.