[SERVER-13176] Wrong code for duplicate key error when downconverting update command Created: 12/Mar/14 Updated: 11/Jul/16 Resolved: 14/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.0-rc1 |
| Fix Version/s: | 2.6.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL | |||||||||||||||||||||||
| Steps To Reproduce: | A shard running 2.4, mongos 2.6.
If the shard is running 2.6, the error code is the expected 11000. |
|||||||||||||||||||||||
| Participants: |
| Description |
|
When a client executes the "update" command on mongos, and mongos sends OP_UPDATE to a shard, and the shard's GLE responds with a duplicate key error, mongos must convert the error code to 11000. However, mongos allows the code 11001 through to the client. Clients written to raise a specific exception class for duplicate key errors in response to write commands only anticipate code 11000. |
| Comments |
| Comment by Githook User [ 14/Mar/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Githook User [ 14/Mar/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |