[SERVER-33183] Remove convertToCapped from OplogEntry::CommandType Created: 08/Feb/18  Updated: 29/Oct/23  Resolved: 07/Oct/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Minor - P4
Reporter: William Schultz (Inactive) Assignee: Anthony Perkins (Inactive)
Resolution: Fixed Votes: 0
Labels: former-quick-wins, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-29904 don't generate convertToCapped oplog ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-09-21, Repl 2020-10-05, Repl 2020-10-19
Participants:

 Description   

The changes from SERVER-29904 made it so that the convertToCapped command was no longer replicated as a special oplog entry. It was simply converted into the equivalent DDL operations and those were replicated via the oplog just the same as any other normal collection operations. Since the convertToCapped command will no longer show up in the oplog as such, we should be able to remove the type from the OplogEntry class.



 Comments   
Comment by Githook User [ 05/Oct/20 ]

Author:

{'name': 'Anthony Perkins', 'email': 'anthony.perkins@mongodb.com', 'username': 'tony-mongodb'}

Message: SERVER-33183 Removed the kConvertToCapped type from OplogEntry class
Branch: master
https://github.com/mongodb/mongo/commit/b35660b90b6c359379ddd72c1d2655ecb10f5cac

Comment by Spencer Brody (Inactive) [ 13/Feb/18 ]

We removed this in 3.6. We should probably wait an extra version before removing support for this, just to be extra cautious against someone who upgrades two versions quickly, without their oplog rolling over.

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