[SERVER-36925] All write operations with a query component should support readConcern Created: 29/Aug/18  Updated: 13/Sep/18  Resolved: 13/Sep/18

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

Type: New Feature Priority: Major - P3
Reporter: Bernie Hackett Assignee: Asya Kamsky
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-20445 Add support for majority read concern... Closed
Sprint: Query 2018-09-24
Participants:

 Description   

Follow on from SERVER-20445 where we're adding readConcern majority support to mapReduce with non-inline output and aggregate with $out. We should probably be consistent about write operations that have a query component. For example, the update and delete commands.



 Comments   
Comment by Asya Kamsky [ 13/Sep/18 ]

Since the write operations can currently only rely on the document itself (update must use current version of the document values to update itself) we will not be supporting this until that's no longer the case.

Comment by Andy Schwerin [ 30/Aug/18 ]

I'm not certain about this. In particular, write operations should typically operate on the most recent version. If we change the system to allow updates or deletes to select based on joined data, then a reacConcern will be meaningful, but for now, I think all it could do is increase the abort rate when an update decision is made based on a stale version of a document and then aborts.

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