[SERVER-34932] [change streams] Adjust resume token (if necessary) for sharded transactions Created: 10/May/18  Updated: 27/Oct/23  Resolved: 20/Feb/19

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

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Team (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-35888 Improve resumeToken to support resumi... Closed
Related
is related to SERVER-34554 Database drops do not have a total or... Backlog
Assigned Teams:
Query
Operating System: ALL
Participants:

 Description   

Depending on the format of a transaction in the oplog, we will likely have to update the format of the resume token to ensure we have a total ordering across all operations, particularly those that commit as part of a distributed, multi-document transaction.



 Comments   
Comment by Justin Seyster [ 20/Feb/19 ]

Our design for "Change Streams support for sharded transactions" determined that we don't need any changes to the resume token.

Comment by Kaloian Manassiev [ 11/Jun/18 ]

Thanks - this sounds fine to me. We are still working on the design and someone from query will be included to review the interaction with change streams.

Comment by Ian Whalen (Inactive) [ 08/Jun/18 ]

kaloian.manassiev this is still query work but we wanted to add it to your project just to make sure cross-shard transactions didn't get resolved without thinking about changestreams.

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