[SERVER-47861] Investigate consolidation of readConcern validation Created: 30/Apr/20 Updated: 06/Dec/22 Resolved: 25/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
Presently, we have validation of readConcern that occurs in a few places in the code. This can lead to some unexpected consequences, such as read concern validation occurring later than expected (see We should investigate whether it's possible to merge the validation that occurs at the service entry point level with the validation that occurs in the replication coordinator, provided that the read concern is not expected to change between these two code locations. |
| Comments |
| Comment by Steven Vannelli [ 25/May/21 ] |
|
Closing this out as the team doesn't feel this is a priority at the moment. |
| Comment by Connie Chen [ 01/Mar/21 ] |
|
The scope of this work may have changed due to updates to the service entry point level validation, sending this to Service Arch to triage. |