[SERVER-60102] Ensure clustered collections must be dropped before downgrade Created: 20/Sep/21  Updated: 29/Oct/23  Resolved: 09/Nov/21

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Josef Ahmad
Resolution: Fixed Votes: 0
Labels: PM-2311-M1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-11-01, Execution Team 2021-11-15
Participants:

 Description   

There should be a test for the downgrade path that non-timeseries clustered collections must be dropped before downgrading from 5.1 to 5.0



 Comments   
Comment by Githook User [ 09/Nov/21 ]

Author:

{'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}

Message: SERVER-60102 Clustered collection downgrade paths 5.2->5.1 and 5.2->5.0
Branch: master
https://github.com/mongodb/mongo/commit/c55e853ba4694091782a3dc40933a57903875745

Comment by Githook User [ 03/Nov/21 ]

Author:

{'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}

Message: SERVER-60102 Validate clustered collections must be dropped to downgrade to 5.0
Branch: master
https://github.com/mongodb/mongo/commit/837239bbd18c9d84ea5b57af80ffaabe7e5f9a73

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