[SERVER-33825] the E11000 duplicate key error looks different on each storage engine Created: 12/Mar/18 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Miguel Angel Nieto | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The ouput message for the 11000 should be the same regardless of the storage engine, but it is implemented different on each storage engine. For example: ephemeralForTest:
WiredTiger:
mmapv1:
|
| Comments |
| Comment by Miguel Angel Nieto [ 27/Mar/18 ] |
|
ian.whalen yes, I am trying to parse. That is the issue. With the current implementation, you would need different ways to parse the same error, depending on the storage engine. The output should be similar to make the experience consistent across different storage engines. |
| Comment by Ian Whalen (Inactive) [ 16/Mar/18 ] |
|
miguel.nieto are you trying to parse these strings? Or is this an issue for some other reason? |