[SERVER-66138] Remove support for 'o2.type' fields for no-op oplog entries in change streams code Created: 03/May/22  Updated: 29/Oct/23  Resolved: 27/Jul/23

Status: Closed
Project: Core Server
Component/s: Change streams, Internal Code
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Arun Banala Assignee: Victor Ghita (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Sprint: QE 2023-05-15, QE 2023-05-29, QE 2023-06-12, QE 2023-06-26, QE 2023-07-10, QE 2023-07-24, QE 2023-08-07
Participants:

 Description   

After SERVER-65909, we will no longer log the 'o2.type' field for no-op oplog entries. We have retained handling these fields in the change streams code for backwards compatibility. After 7.0 release we can remove this code.



 Comments   
Comment by Githook User [ 25/Jul/23 ]

Author:

{'name': 'Victor Ghita', 'email': 'victor.ghita@mongodb.com', 'username': ''}

Message: SERVER-66138 Remove support for 'o2.type' fields for no-op oplog entries in change streams code
Branch: master
https://github.com/mongodb/mongo/commit/9b0b48147b3cea9372d2829d457b002069018b3d

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