[SERVER-32128] Test that all collections have UUIDs on clean startup in master branch and disable/remove all other parts of set_schema_version.js. Created: 30/Nov/17  Updated: 30/Oct/23  Resolved: 27/Dec/17

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 3.7.1

Type: Task Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-32188 Have secondaries apply timestamps to ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-12-18, Storage 2018-01-01
Participants:

 Description   

The set_schema_version.js test primarily tests 3.4 to 3.6-specific upgrade cases, but it also ensures that all collections have UUIDs on clean startup. This is still necessary to test in master because it is an issue of collections being created prior to setting the featureCompatibilityVersion to 3.6 on clean startup rather than an upgrade/downgrade issue (see SERVER-30131/SERVER-31792). The rest of the UUID checking should be removed and the other parts of the test should be disabled until the featureCompatibilityVersion is bumped.



 Comments   
Comment by Githook User [ 27/Dec/17 ]

Author:

{'email': 'maria@mongodb.com', 'username': 'mvankeulen94', 'name': 'Maria van Keulen'}

Message: SERVER-32128 Disable upgrade/downgrade testing in set_schema_version.js
Branch: master
https://github.com/mongodb/mongo/commit/ef6471345974d763d82b7aa2020f80eb59903b6f

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