-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Drivers are inconsistent in their handling of a "ns not found" error returned by the server. We should codify this behavior in a specification, and ensure that all drivers conform.
Description of Linked Ticket
https://stackoverflow.com/questions/37136204/mongoerror-ns-not-found-when-try-to-drop-collection
Mongo should say WHICH collection was not found.
- depends on
-
CDRIVER-3392 Improve unhelpful error "ns not found"
- Closed
-
CSHARP-2791 Improve unhelpful error "ns not found"
- Closed
-
CXX-1847 Improve unhelpful error "ns not found"
- Closed
-
MOTOR-426 Improve unhelpful error "ns not found"
- Closed
-
NODE-2252 Ignore "ns not found" error
- Closed
-
PHPC-1455 Improve unhelpful error "ns not found"
- Closed
-
PHPLIB-488 Improve unhelpful error "ns not found"
- Closed
-
PYTHON-2010 Improve unhelpful error "ns not found"
- Closed
-
RUBY-1963 Improve unhelpful error "ns not found"
- Closed
-
GODRIVER-1630 Specify how drivers handle "ns not found" errors
- Closed
-
JAVA-3462 Improve unhelpful error "ns not found"
- Closed
-
RUST-451 Specify how drivers handle "ns not found" errors
- Closed
-
SERVER-41365 Improve unhelpful error "ns not found"
- Closed
- related to
-
DRIVERS-1253 Make dropIndexes abort in-progress index builds
- Closed