[DRIVERS-942] Consider resuming on aggregate for change streams Created: 21/Feb/20 Updated: 12/Jan/24 Resolved: 13/Dec/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Change Streams, Retryability |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Divjot Arora (Inactive) | Assignee: | Kyle Kloberdanz |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | jeff+ | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||
| Quarter: | FY24Q4 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Engineering Lead: | |
||||||||||||||||||||||||||||||||||||||||||||||||
| Start date: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
|
| Comments |
| Comment by Kyle Kloberdanz [ 13/Dec/23 ] |
|
Closing as "Won't Do" for the following reason: Given that aggregate is already retryable, it doesn't seem to add much value to also make it resumable. A few ideas that we considered are below:
|
| Comment by Prashant Mital (Inactive) [ 08/Sep/20 ] |
|
divjot.arora and I propose in light of the above comments that we don't do this. Divjot noted that network errors often occur due to things like expired/invalid certs in which case we don't really want to retry the initial aggregate more so than retryable reads already does. If jeff.yemin and shane.harvey concur, we are happy to close this as Wont Do. |
| Comment by Shane Harvey [ 08/Sep/20 ] |
|
To add some more context here: The initial aggregate command issued by watch() is already retryable according to the retryable reads spec. For an example see the "db.coll.watch succeeds on second attempt" test. |
| Comment by Jeffrey Yemin [ 21/Feb/20 ] |
|
From a chat with bernard.gorman
|