[JAVA-757] Exceptions throws for GLE should contain the entire GLE document Created: 12/Feb/13 Updated: 19/Mar/13 Resolved: 25/Feb/13 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | None |
| Affects Version/s: | 2.10.1 |
| Fix Version/s: | 2.11.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Currently, you get the code and the err fields from the result document, and the code is not included in the exception message so it's generally lost. To fix, adding a new MongoException subclass called WriteConcernException, which DuplicateKey now extends. WriteConcernException takes the command result and passes toString() of it to MongoException, so the JSON representation of the entire document will appear in logs, e.g.
|
| Comments |
| Comment by auto [ 14/Mar/13 ] |
|
Author: {u'date': u'2013-03-14T19:30:20Z', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |
| Comment by auto [ 22/Feb/13 ] |
|
Author: {u'date': u'2013-02-15T22:32:15Z', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |
| Comment by auto [ 22/Feb/13 ] |
|
Author: {u'date': u'2013-02-13T02:36:20Z', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |
| Comment by auto [ 22/Feb/13 ] |
|
Author: {u'date': u'2013-02-12T17:09:41Z', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |