[SERVER-41573] Make it easier for command paths to return early on writeConcern errors Created: 06/Jun/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Execution
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
As we discussed at the offsite, this could be accomplished by adding the writeConcern error info as ExtraErrorInfo on a WriteConcernfailed status and having the service entry point on mongos catch WriteConcernFailed and attach the writeConcern info to the response object. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 22/Jul/19 ] |
|
I'm not sure, but maybe because the linked PM-920 is on the query backlog.... and if we did PM-920, this request would no longer be applicable. |