[SERVER-56669] Separate change streams buildPipeline() method for legacy and when change stream optimizations are enabled Created: 05/May/21  Updated: 29/Oct/23  Resolved: 31/May/21

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

Type: Improvement Priority: Major - P3
Reporter: Arun Banala Assignee: Arun Banala
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-05-17, Query Execution 2021-05-31, Query Execution 2021-06-14
Participants:

 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 31/May/21 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-56669 Refactor change streams stage building logic
Branch: master
https://github.com/mongodb/mongo/commit/3cf2bc8bfc833f9d2b044b2b3da611819409cc8d

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