-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
(copied to CRM)
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.