[SERVER-40446] Add NonResumableChangeStreamError Created: 02/Apr/19  Updated: 29/Oct/23  Resolved: 25/Apr/19

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

Type: New Feature Priority: Major - P3
Reporter: Katherine Walker (Inactive) Assignee: Justin Seyster
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to DRIVERS-650 ChangeStream spec's Resumable Error d... Closed
related to SERVER-39675 Look up prepared transaction when a C... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2019-05-06
Participants:

 Description   

The error label NonRetryableChangeStreamError was added to error_codes.err in SERVER-39675. It looks like the error label still needs to be fully implemented as a ChangeStreamFatalError does not have the error label. Also, it may make more sense to refer to this type of error as NonResumableChangeStreamError instead of NonRetryableChangeStreamError.



 Comments   
Comment by Githook User [ 25/Apr/19 ]

Author:

{'email': 'justin.seyster@mongodb.com', 'name': 'Justin Seyster', 'username': 'jseyster'}

Message: SERVER-40446 Add "NonResumableChangeStreamError" error label

Give the "NonRetryableChangeStreamError" error class a more
appropriate name and propagate it to an "errorLabel" in the command
response.
Branch: master
https://github.com/mongodb/mongo/commit/0e9564888a31af6b49afb7a6106301bc16ae6956

Comment by Katherine Walker (Inactive) [ 09/Apr/19 ]

That works for us!

Comment by David Storch [ 09/Apr/19 ]

Thanks for bringing this to our attention katherine.walker! We plan to have these suggested changes implemented in our upcoming sprint, so we hope to have the fix merged by May 6. Does this work for the drivers team schedule?

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