[CXX-1748] read_concern support for individual operations Created: 26/Mar/19  Updated: 07/Feb/24

Status: Backlog
Project: C++ Driver
Component/s: API
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Henrik Ingo (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to CXX-1749 mongocxx api doc: read_concern can al... Backlog
Epic Link: C++ Developer Experience Improvements
Quarter: FY24Q4

 Description   

Unlike write_concern and read_preference, I cannot set read_concern for individual operations like mongocxx::options::find, mongocxx::options::update & co. It would make sense for read_concern to be supported in all the same contexts as write_concern + matching read operations.



 Comments   
Comment by Kevin Albertson [ 04/Apr/19 ]

As a reminder to myself, we are CRUD spec compliant, in that read_concern/write_concern/read_preference does not need to be settable on operation level:
https://github.com/mongodb/specifications/blob/master/source/crud/crud.rst#q--a

But since we have write_concern and read_preference, I agree we should add read_concern for consistency.

Generated at Wed Feb 07 22:03:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.