read_concern support for individual operations

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: API
    • None
    • None
    • None
    • None
    • None
    • None

      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.

        1.
        		 Add read_concern to insert options classes CXX-3445 Sub-task Backlog Unassigned  
        2.
        		 Add read_concern to replace options classes CXX-3446 Sub-task Backlog Unassigned  
        3.
        		 Add read_concern to delete options classes CXX-3447 Sub-task Backlog Unassigned  
        4.
        		 Add read_concern to bulk_write options classes CXX-3448 Sub-task Backlog Unassigned  
        5.
        		 Add read_concern to index options classes CXX-3449 Sub-task Backlog Unassigned  
        6.
        		 Add read_concern to findOneAnd* options classes CXX-3450 Sub-task Backlog Unassigned  
        7.
        		 Add read_concern to count options classes CXX-3451 Sub-task Backlog Unassigned  
        8.
        		 Add read_concern to distinct options classes CXX-3452 Sub-task Backlog Unassigned  
        9.
        		 Add read_concern to estimated_document_count options classes CXX-3453 Sub-task Backlog Unassigned  

            Assignee:
            Ezra Chung
            Reporter:
            Henrik Ingo (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: