[SERVER-23186] readConcerns other than "local" should be rejected on non-replicated collections (like local db) Created: 16/Mar/16  Updated: 06/Dec/22  Resolved: 04/Nov/16

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

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9541 Docs for SERVER-23186: readConcerns o... Closed
Related
related to SERVER-23185 writeConcern w levels other than 0 an... Closed
Assigned Teams:
Replication
Backwards Compatibility: Major Change
Operating System: ALL
Participants:

 Description   

Oplog entries have the same readConcern visibility as the writes that they represent. For other collections in the local database, non-local readConcerns don't make sense.

Other non-replicated collections include:

  • <db>.system.profile


 Comments   
Comment by Ian Whalen (Inactive) [ 26/Apr/19 ]

Switching "Drivers Changes Needed" from "Maybe" to "Not Needed" since this was closed as something other than Fixed.

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