[SERVER-35380] Log parsed BSON on missing expected fields Created: 04/Jun/18 Updated: 29/Oct/23 Resolved: 07/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Ben Judd |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Storage NYC 2018-06-18 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Comments |
| Comment by Githook User [ 07/Jun/18 ] |
|
Author: {'username': 'Icantjuddle', 'name': 'Ben Judd', 'email': 'ben.judd@10gen.com'}Message: |
| Comment by Eric Milkie [ 04/Jun/18 ] |
|
The idea here is to log a message with the BSON that we were parsing. This would make it more obvious what went wrong when diagnosing BF tickets such as the one that was linked. Keep in mind that we need to redact any output in the log, so we'll need to call the redact() function. The commit for this ticket should look something like cloner.cpp:275. |