[DOCS-15288] Investigate changes in SERVER-64970: Start generating new v2 resume token format for all events by default Created: 28/Apr/22  Updated: 07/Jun/22  Resolved: 07/Jun/22

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Jeffrey Allen
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-64970 Start generating new v2 resume token ... Closed
Participants:
Days since reply: 1 year, 35 weeks, 1 day ago
Epic Link: DOCSP-21764

 Description   
Original Downstream Change Summary

This change introduces a new resume token format (v2). Both 6.0 and 7.0 servers can understand the v1 and v2 format. If there are any internal teams that decode the resume token, they might be impacted.

Description of Linked Ticket

After 6.0, we should start generating the new, standardised token format for all events. This will require us to set the default token version to 2, to make $_generateV2ResumeTokens an optional parameter, and to have mongoS and mongoD assume that its value is true unless it is present and explicitly false. This ticket should also include upgrade/downgrade work to ensure that a change stream can survive upgrades between 6.0 and later releases.



 Comments   
Comment by Jeffrey Allen [ 07/Jun/22 ]

Chatted with arun.banala@mongodb.com on this and we don't provide any utility to decode a resume token, so users won't see any impact here. Closing this ticket.

Comment by Education Bot [ 28/Apr/22 ]

Fix Version updated for upstream SERVER-64970:
6.1.0-rc0

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