[SERVER-79930] Name all document constraint errors Created: 11/Aug/23  Updated: 12/Sep/23

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

Type: Task Priority: Major - P3
Reporter: Dave Rolsky Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Query Execution
Participants:

 Description   

We are using these codes in Mongosync and it would be nice if they were named. It would even nicer if the actual errors returned all shared a label. The codes we're using are 16746, 16755, 16766, and 16804, but there may be other codes for similar errors that we haven't seen in our testing.



 Comments   
Comment by Dave Rolsky [ 05/Sep/23 ]

It's not terribly high priority. It's really just something that would make our Mongosync codebase a bit cleaner.

Comment by Amr Elhelw [ 05/Sep/23 ]

dave.rolsky@mongodb.com What the priority of this ask?

Comment by Dave Rolsky [ 22/Aug/23 ]

jian.guan@mongodb.com That error isn't a document constraint error so it probably needs a new ticket.

Comment by Jian Guan [ 22/Aug/23 ]

Adding error code 7182803 to this list.

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