[DOCS-4853] [Server] WriteResult.writeError may have errInfo field Created: 20/Feb/15 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Jeremy Mikola | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, reopened, request, server-docs-bug-bash, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||
| Description |
|
Per the Write Command Specification:
In the WriteResult documentation, we only discuss an errInfo field on WriteResult.writeConcernError. I think it may need to go on WriteResult.writeError as well (since the spec mentions it could occur with sharding). On that note, I have no idea what the sharding error might be. It'd be helpful to have a kernel engineer confirm for us before we document it. Additionally, knowing how to trigger such an error would be helpful for driver authors implementing the CRUD API spec, which has guidelines for error handling. |
| Comments |
| Comment by Sarah Olson [ 01/Nov/22 ] |
|
Thanks for the additional detail jmikola@mongodb.com! |
| Comment by Jeremy Mikola [ 01/Nov/22 ] |
|
This is still relevant. Since I opened this ticket, DRIVERS-820 was implemented and notes that a write error's errInfo field may relay information about failed document validation. |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |