[JAVA-1388] Handle embedded "ns not found" errmsg from mongos Created: 18/Aug/14 Updated: 30/Jan/15 Resolved: 25/Sep/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Error Handling |
| Affects Version/s: | None |
| Fix Version/s: | 2.13.0, 3.0.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
When running deleteIndexes command against a mongos on a non-existing collection, mongos returns:
Currently the driver is unable to swallow that error, as it does against a mongod, which just returns:
because the driver is simply looking for an errmsg that equals "ns not found". |
| Comments |
| Comment by Githook User [ 30/Jan/15 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |
| Comment by Jeffrey Yemin [ 29/Jan/15 ] |
|
2.13.0 has been released. Closing issue. |
| Comment by Githook User [ 25/Sep/14 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: To ensure that dropIndexes and drop on DBCollection don't throw an exception if the collection does not exist,
|
| Comment by Githook User [ 18/Aug/14 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |