[SERVER-78458] Allow statuses/assertions to have both a named error code and a unique number Created: 26/Jun/23  Updated: 03/Jul/23  Resolved: 03/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Backlog - Service Architecture
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Related
is related to SERVER-73524 Report a histogram of error codes rat... Open
is related to SERVER-73561 Consider exception origin when counti... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

Currently statuses/assertions can have either a named error code or a unique number. Named error codes are useful for cases which are semantically the same from the user's point of view. However for diagnosability/debuggability, unique numbers can be very helpful because you can immediately tell exactly where an error came from. So it might be nice to be able to include a unique number together with a named code, for instance in a uassert.



 Comments   
Comment by Phoebe Du [ 03/Jul/23 ]

Will be addressed in a Project https://jira.mongodb.org/browse/PM-3400

Generated at Thu Feb 08 06:38:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.