-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
All commands that write can accept write concern should have a standard way of reporting write concern errors. When a command succeeds but fails waiting for write concern, the command response indicates ok:1, but has a writeConcernError field. User management commands, however, report errors differently - a failed write concern for them causes the whole command to report ok:0.
Drivers need to update handling of write concern errors by user management commands to be the same as any other command.
- depends on
-
CDRIVER-2900 Update handling of write concern errors by user management commands
- Backlog
-
CXX-1703 Update handling of write concern errors by user management commands
- Blocked
-
CSHARP-2451 Update handling of write concern errors by user management commands
- Closed
-
GODRIVER-689 Update handling of write concern errors by user management commands
- Closed
-
JAVA-3120 Update handling of write concern errors by user management commands
- Closed
-
MOTOR-293 Update handling of write concern errors by user management commands
- Closed
-
NODE-1792 Update handling of write concern errors by user management commands
- Closed
-
PHPC-1304 Update handling of write concern errors by user management commands
- Closed
-
PYTHON-1703 Update handling of write concern errors by user management commands
- Closed
-
RUBY-1613 Update handling of write concern errors by user management commands
- Closed
-
SERVER-28871 Remove write concern error backwards compatibility for user management commands
- Closed