[SERVER-38686] [createIndex response format] mongos createIndex should prioritize other errors over CannotImplicitlyCreateCollection Created: 18/Dec/18 Updated: 06/Dec/22 Resolved: 06/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.1.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | open_todo_in_code, todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
Currently, if shard returns multiple errors, createIndex simply selects the first error it saw and puts it on the top level error field. Instead, it should prioritize other errors over CannotImplicitlyCreateCollection. |
| Comments |
| Comment by Githook User [ 12/Aug/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit b3ccc75e5aa4b182e0859f8e862e1248425c30d4) |
| Comment by Githook User [ 30/Jun/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit b3ccc75e5aa4b182e0859f8e862e1248425c30d4) |
| Comment by Githook User [ 04/May/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |
| Comment by Randolph Tan [ 18/Dec/18 ] |
|
Or, if we can make mongos send createIndex to shards with chunks correctly (with shard version), we won't need to do this. |