[SERVER-11735] dbcase.js/dbcase2.js fail in sharding passthrough if write commands is enabled Created: 15/Nov/13 Updated: 07/Oct/15 Resolved: 16/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | 3.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | YunHe Wang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Quint 9 09/18/15 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
dbcase.js and dbcase2.js pass if run directly without mongos using write commands. It looks like there is a different in the formatting of the returned object: direct to mongod: { "errmsg" : "exception: db already exists with different case other: [dbcasetest_dbnamea] me [dbcasetest_dbnameA]", "code" : 13297, "ok" : 0 }through mongos: { "$err" : "error creating initial database config information :: caused by :: can't have 2 databases that just differ on case have: dbcasetest_dbnamea want to add: dbcasetest_dbnameA", "code" : 13297 } |
| Comments |
| Comment by Githook User [ 16/Sep/15 ] |
|
Author: {u'username': u'yhjw88', u'name': u'Yunhe (John) Wang', u'email': u'yunhe.wang@mongodb.com'}Message: |
| Comment by YunHe Wang [ 14/Sep/15 ] |
|
Replacing the explicit error code checks with "write failed" |
| Comment by Githook User [ 07/Oct/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |