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

Status: Closed
Project: Core Server
Component/s: 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-50636 Write reshardDoneCatchUp no-op oplog ... 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: "reshardDoneCatchUp",
    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 [ 11/Aug/21 ]

Author:

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

Message: SERVER-50637 Expose reshardDoneCatchUp no-op oplog entry as change event
Branch: v5.0
https://github.com/mongodb/mongo/commit/3be1e000ea09a88202cf7bf754d4d490ba2863e7

Comment by Githook User [ 20/Jul/21 ]

Author:

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

Message: SERVER-50637 Expose reshardDoneCatchUp no-op oplog entry as change event
Branch: master
https://github.com/mongodb/mongo/commit/90ad147363889be0f01c4668dda6323cb7ab8eb2

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