[DRIVERS-745] Specify how drivers handle "ns not found" errors Created: 07/Oct/19  Updated: 09/Jul/20  Resolved: 09/Jul/20

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-3392 Improve unhelpful error "ns not found" Closed
depends on CSHARP-2791 Improve unhelpful error "ns not found" Closed
depends on CXX-1847 Improve unhelpful error "ns not found" Closed
depends on MOTOR-426 Improve unhelpful error "ns not found" Closed
depends on NODE-2252 Ignore "ns not found" error Closed
depends on PHPC-1455 Improve unhelpful error "ns not found" Closed
depends on PHPLIB-488 Improve unhelpful error "ns not found" Closed
depends on PYTHON-2010 Improve unhelpful error "ns not found" Closed
depends on RUBY-1963 Improve unhelpful error "ns not found" Closed
depends on GODRIVER-1630 Specify how drivers handle "ns not fo... Closed
depends on JAVA-3462 Improve unhelpful error "ns not found" Closed
depends on RUST-451 Specify how drivers handle "ns not fo... Closed
depends on SERVER-41365 Improve unhelpful error "ns not found" Closed
Related
related to DRIVERS-1253 Make dropIndexes abort in-progress in... Closed
Driver Compliance:
Key Status/Resolution FixVersion
MOTOR-426 Won't Fix
CSHARP-2791 Won't Fix
NODE-2252 Won't Fix
PYTHON-2010 Won't Fix
RUBY-1963 Won't Fix
CXX-1847 Won't Fix
CDRIVER-3392 Won't Fix
PHPLIB-488 Won't Fix
PHPC-1455 Won't Fix
JAVA-3462 Won't Fix
GODRIVER-1630 Won't Fix
RUST-451 Won't Fix
SWIFT-874 Won't Fix

 Description   
Downstream Change Summary

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.



 Comments   
Comment by Bernie Hackett [ 09/Jul/20 ]

Replaced by the more comprehensive DRIVERS-1323.

Comment by Dianna Hohensee (Inactive) [ 20/May/20 ]

SERVER-41365 has been closed as Won't Do. It was agreed via email that Drivers would take on the work necessary to surface an improved error message to the end user. Server will not make any changes to the error message string in order to avoid breaking compatibility with old driver versions that expect an exact string match.

Comment by Jeremy Mikola [ 08/May/20 ]

shane.harvey: It doesn't look like there was never a downstream DRIVERS ticket for SERVER-37726 but I think we need one. This seems like something that is likely broken today and may simply have gone unnoticed.

A separate DRIVERS ticket immediately created for 4.4 may be preferable if this ticket and SERVER-41365 are going to be deferred until 4.6. I don't recall the full history of this ticket, but it also seems a bit premature to have language tickets created if the server change is only still being investigated.

cc: esha.bhargava alexander.golin

EDIT: DRIVERSP-411 already existed, but had been closed. It has since been re-opened as DRIVERS-1253.

Comment by Shane Harvey [ 07/May/20 ]

FYI: SERVER-37726 (which is included in 4.4) changed the error message for dropIndexes from "ns not found" to "ns not found <db.collection>". This is a similar BC break that drivers may need to work around (see PYTHON-2129).

Comment by Bernie Hackett [ 07/May/20 ]

This is in 4.5, and it doesn't look like it's being backported. I agree, this would seem to violate the versioned API idea that applications that work against 4.4 should continue to work with the versioned API.

Generated at Thu Feb 08 08:22:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.