-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
Platform 4 06/05/15
Right now we catch AssertionException/UserException multiple times and duplicate the same logic for generating error responses throughout the command execution pipeline.
We should make one method to generate an error reply, and let all exceptions bubble up to a canonical place where it is called.
- is depended on by
-
SERVER-18236 Refactor metadata to use OP_COMMAND metadata object
- Closed