[JAVA-1413] Inconsistent Exception handling for dropIndexes on mongod versus mongos Created: 27/Aug/14  Updated: 24/Sep/14  Resolved: 24/Sep/14

Status: Closed
Project: Java Driver
Component/s: Command Operations
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Cailin Nelson Assignee: Jeffrey Yemin
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates JAVA-1388 Handle embedded "ns not found" errmsg... Closed
Related

 Description   

This line will throw an Exception if the driver is talking to a mongos, but not if the driver is talking to a mongod.

For a mongos, the message that the driver is calling .equals on looks like:

"errmsg" : "{ red_0/cailinmac:28000,cailinmac:28001,cailinmac:28002: \"ns not found\" }"

whereas for a mongod the message looks like:

"errmsg" : "ns not found"

This causes an Exception to be raised in the mongos case but not the mongod case.


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