Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
Description
When running deleteIndexes command against a mongos on a non-existing collection, mongos returns:
{
|
"raw" : {
|
"shard02/new-host-4.home:27021,new-host-4.home:27022,new-host-4.home:27023" : {
|
"ok" : 0,
|
"errmsg" : "ns not found"
|
}
|
},
|
"ok" : 0,
|
"errmsg" : "{ shard02/new-host-4.home:27021,new-host-4.home:27022,new-host-4.home:27023: \"ns not found\" }"
|
}
|
Currently the driver is unable to swallow that error, as it does against a mongod, which just returns:
{ "ok" : 0, "errmsg" : "ns not found" }
|
because the driver is simply looking for an errmsg that equals "ns not found".
Attachments
Issue Links
- is duplicated by
-
JAVA-1413 Inconsistent Exception handling for dropIndexes on mongod versus mongos
-
- Closed
-