[SERVER-55438] Move applyOps unwinding logic to its own internal pipeline stage Created: 22/Mar/21  Updated: 29/Oct/23  Resolved: 16/Apr/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Justin Seyster Assignee: Rishab Joshi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-54676 Serialization and deserialization for... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-04-05, Query Execution 2021-04-19, Query Execution 2021-05-03
Participants:

 Description   

Currently, applyOps unwinding happens in the DocumentSourceChangeStreamTransform stage (via the TransactionOpIterator). This logic is largely independent of the transform logic, however, and moving it into its own stage would improve the modularity of change streams pipelines.



 Comments   
Comment by Githook User [ 16/Apr/21 ]

Author:

{'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}

Message: SERVER-55438 Create DocumentSourceChangeStreamUnwindTransactions stage
to unwind transactions
Branch: master
https://github.com/mongodb/mongo/commit/8704b47b32b26465a3030dfe6cbeb1a3b91d3df5

Generated at Thu Feb 08 05:36:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.