[SERVER-8168] Better message when accessing a BSON object field that does not exist Created: 14/Jan/13  Updated: 10/May/22

Status: Backlog
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 2.3.2
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Randolph Tan Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently, it displays:

assertion: 13111 field not found, expected type <n>

where <n> is the BSON type. It would be nice if the error would also print out the field name to make debugging much easier.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Mira Carey [ 23/May/16 ]

renctan,

If you want this, go for it, but we're going to put it off a bit for now.

Generated at Thu Feb 08 03:16:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.