[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: |
|
||||||||||||
| Sprint: | Query 2018-09-24 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Follow on from |
| 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. |