[SERVER-45708] Add automated test for downgrading with change streams Created: 22/Jan/20  Updated: 29/Oct/23  Resolved: 10/Jun/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Arun Banala
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-05-04, Query 2020-05-18, Query 2020-06-01, Query 2020-06-15
Participants:

 Description   

We have automated tests for the upgrade scenarios, but nothing to test that downgrade behaves appropriately. Specifically, we should at least test that the older versions do not crash when reading oplog entries that they do not understand from the newer version.



 Comments   
Comment by Githook User [ 10/Jun/20 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-45708 Add automated test for downgrading with change streams
Branch: master
https://github.com/mongodb/mongo/commit/bacc717789965d83d5253a4591c5f3171c741c39

Comment by Charlie Swanson [ 22/Jan/20 ]

tess.avitabile suggests that we put this on the backlog and schedule it as part of PM-1460, which I think is a reasonable suggestion. It seems like the next query project that will have an impact on the oplog.

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