[SERVER-50522] Expose reshardBegin no-op oplog entry as change event Created: 25/Aug/20  Updated: 29/Oct/23  Resolved: 15/Jul/21

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

Type: New Feature Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Matthew Walak (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-O-unspecialized, PM-234-T-change-streams, query-work-resharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-50521 Write reshardBegin no-op oplog entry ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding 2021-07-12, Sharding 2021-07-26
Participants:
Story Points: 1

 Description   

Convert the repl::OpTypeEnum::kNoop entry into a change event of the form:

{
    operationType: "reshardBegin",
    reshardingUUID: <reshardingUUID>,
}



 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 [ 10/Aug/21 ]

Author:

{'name': 'mrwalak', 'email': 'matt.walak@mongodb.com'}

Message: SERVER-50522 Expose reshardBegin no-op oplog entry as change event
Branch: v5.0
https://github.com/mongodb/mongo/commit/0f20c10b9007e99aa83fc167ede6caa58e2e6d0e

Comment by Githook User [ 15/Jul/21 ]

Author:

{'name': 'mrwalak', 'email': 'matt.walak@mongodb.com'}

Message: SERVER-50522 Expose reshardBegin no-op oplog entry as change event
Branch: master
https://github.com/mongodb/mongo/commit/0aa98bed9ee0c2f10a577b4ad63d068cc7b9a5af

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