-
Type: New Feature
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Service Arch
It would be helpful for driver testing if errorLabels could be specified as part of a failCommand failpoint. Alternatively, the errorLabels could simply populated according to the error code's category as they are for real errors.
Also, I'm required to set an assignee for this, but wasn't exactly sure where to send it. I apologize in advance if the platform team backlog is not the correct place.
Edit: upon further inspection, I've found that the alternative mentioned above is how failCommand currently works. i.e. The server is setting errorLabels according to the category (e.g. 280 and NonResumableChangeStreamError). That makes this work lower priority, but it would probably still be useful if drivers could trigger errors with specific labels in their tests.
- duplicates
-
SERVER-43941 Add "errorLabels" field to failCommand fail point
- Closed