[JAVA-4219] Error Code from WriteError not propagated to MongoServerException Created: 02/Jul/21 Updated: 28/Oct/23 Resolved: 07/Apr/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Error Handling |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.0, 3.12.13 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christoph Strobl | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | external-user | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||||||||||
| Description |
|
The current driver 4.3.0-beta3 does not seem to propagate the error code from the WriteError to the MongoWriteException in case of an E11000. With 4.2 drivers the error code matched.
|
| Comments |
| Comment by Githook User [ 05/Apr/23 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Update test to use 4.x Junit API
|
| Comment by Jeffrey Yemin [ 05/Apr/23 ] |
|
The commit cherrypicks cleanly to 3.12.x, so re-opening this to consider releasing a 3.12.x patch containing the fix, as a user reported this under |
| Comment by Githook User [ 05/Apr/23 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Fix regression in MongoWriteException error code Ensure that the error code from the single WriteError is propagated to the
|
| Comment by Githook User [ 02/Jul/21 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Fix regression in MongoWriteException error code Ensure that the error code from the single WriteError is propagated to the
|
| Comment by Jeffrey Yemin [ 02/Jul/21 ] |
|
Looks like the regression was introduced in the patch for JAVA-3993. Note that JAVA-3993 has not been included in a GA release yet, so this bug shouldn't affect anyone who's not using a 4.3.0 beta release. |