[GODRIVER-824] Support postBatchResumeToken in change streams Created: 11/Feb/19  Updated: 28/Oct/23  Resolved: 07/May/19

Status: Closed
Project: Go Driver
Component/s: CRUD
Affects Version/s: None
Fix Version/s: 1.1.0

Type: New Feature Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Divjot Arora (Inactive)
Resolution: Fixed Votes: 0
Labels: FY2020Q1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-595 Support postBatchResumeToken in chang... Closed
Related
is related to GODRIVER-765 Support 'startAfter' option to the $c... Closed
Epic Link: Godriver 4.2 Support
Backwards Compatibility: Fully Compatible

 Description   

See DRIVERS-595 for details.



 Comments   
Comment by Githook User [ 07/May/19 ]

Author:

{'name': 'Divjot Arora', 'username': 'divjotarora', 'email': 'divjot.arora@10gen.com'}

Message: Support startAfter and postBatchResumeToken in change streams.

GODRIVER-765
GODRIVER-824

Change-Id: I9f646c56bdc3865884f82fd4b230be9a1ffac658
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/e5392abff1e09c191049106a5ec082ed63fbc92d

Comment by Divjot Arora (Inactive) [ 03/May/19 ]

CR: https://review.gerrithub.io/c/mongodb/mongo-go-driver/+/452458

Comment by Divjot Arora (Inactive) [ 26/Apr/19 ]

This is being done in the same patch as GODRIVER-765

Comment by Jeffrey Yemin [ 08/Apr/19 ]

We're pretty close to having specification tests approved for this feature. Once we have that we can schedule this work

Comment by Drew DiPalma (Inactive) [ 08/Apr/19 ]

We did a bit of research on our side to center around priority here.  We see this cause Triggers to become disabled fairly regularly.  

  • 5 tickets related to this within the past 90 day representing ~28% of Triggers related tickets and ~3% of total Stitch tickets
  • Of the 1342 Triggers that are currently live (not deleted), 158 are currently in a failed state that we believe is due to this issue. This represents ~10% of total live triggers and ~21% of Triggers currently in a failed state
  • The only way for a customer to mitigate this is to resume without the token which leads to missed events.  
  • There is no automated way for a customer to find about this failure (though we are starting work on this)
Comment by Eric Daniels (Inactive) [ 04/Apr/19 ]

Yes we need it.

Comment by Ian Whalen (Inactive) [ 11/Feb/19 ]

eric.daniels does stitch need this?

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