[SERVER-50301] Delete code which handles $v:1 update oplog entries Created: 13/Aug/20  Updated: 29/Oct/23  Resolved: 01/Jul/22

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

Type: Task Priority: Minor - P4
Reporter: Ian Boros Assignee: Mihai Andrei
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by TOOLS-3142 Investigate changes in SERVER-50301: ... Closed
Documented
is documented by DOCS-15462 [SERVER] SERVER-50301: Delete code wh... Backlog
Related
related to SERVER-60640 sharding_update_v1_oplog_jscore_passt... Closed
Backwards Compatibility: Minor Change
Sprint: Query Execution 2021-07-12, QE 2021-10-04, QE 2021-10-18, QE 2021-11-01, QE 2021-11-15, QE 2021-11-29, QE 2021-12-13, QE 2021-12-27, QE 2022-01-10, QE 2022-02-07, QE 2022-02-21, QE 2022-01-24, QE 2022-05-16, QE 2022-05-30, QE 2022-06-13, QE 2022-06-27, QE 2022-07-11
Participants:
Linked BF Score: 8

 Description   

The upcoming yearly release will only need to log $v:1 update oplog entries for compatibility with 4.4. When we branch for the subsequent release (4.8/5.0?), we can get rid of a lot of this code.



 Comments   
Comment by Githook User [ 30/Jun/22 ]

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}

Message: SERVER-50301 Delete code which handles $v:1 update oplog entries
Branch: master
https://github.com/mongodb/mongo/commit/17f49ab8b16a6f45371771d8c152cfbf4ed186af

Comment by Ian Boros [ 28/Apr/22 ]

Can we schedule this?

Comment by Ian Boros [ 22/Feb/22 ]

CC arun.banala

Comment by David Storch [ 01/Feb/22 ]

ethan.zhang, do you mean that this ticket is now unscheduled, or do you still intend to complete it, just outside of the context of the upgrade/downgrade project? If it is unscheduled, I think we should mark it for re-triage and implement it in this quarter or next.

Comment by Steven Vannelli [ 31/Jan/22 ]

Thanks for letting me know ethan.zhang!

Comment by Ethan Zhang (Inactive) [ 31/Jan/22 ]

steven.vannelli We decided to backlog this and exclude it from the epic.

Comment by Ethan Zhang (Inactive) [ 16/Sep/21 ]

We probably can knock this out in the next sprint.

Comment by Ian Boros [ 13/Aug/20 ]

This should probably go in some kind of upgrade/downgrade epic for next year.

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