[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: |
|
||||||||||||
| 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:
whereas for a mongod the message looks like:
This causes an Exception to be raised in the mongos case but not the mongod case. |