[SERVER-23785] Remove ShardRegistry::kWriteConcernError in favor of using an error_class Created: 18/Apr/16  Updated: 26/Apr/16  Resolved: 22/Apr/16

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-22540 Commands that do writes on mongos sho... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 13 (04/22/16), Repl 14 (05/13/16)
Participants:

 Description   

https://github.com/mongodb/mongo/commit/889ca31c1a1e7725b14f291233a4ee4f7afea111 introduces an error code set of write concern errors and hung it in the ShardRegistry, even though the only users of this set are the user management commands. This is not the right place for this set to live. Instead we should define an error_class in error_codes.err and use the is*Error method it creates



 Comments   
Comment by Githook User [ 22/Apr/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-23785 create WriteConcernError error class
Branch: master
https://github.com/mongodb/mongo/commit/ffbd2dfcd07a29c5cfb3d087ccfb33cfbc315d07

Generated at Thu Feb 08 04:04:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.