[SERVER-33607] Standard indexes should stay at version 2 when introducing V2Unique Created: 02/Mar/18  Updated: 29/Oct/23  Resolved: 11/Mar/18

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

Type: Improvement Priority: Major - P3
Reporter: Sulabh Mahajan Assignee: Sulabh Mahajan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-33458 With index version bump, update jstes... Closed
is duplicated by SERVER-33459 Investigate test failures in sharding... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage Non-NYC 2018-03-12
Participants:

 Description   

With FCV 4.0 unique indexes are to be created with version V2Unique. The standard indexes and _id indexes should stay at version V2.



 Comments   
Comment by Githook User [ 11/Mar/18 ]

Author:

{'email': 'sulabh.mahajan@mongodb.com', 'name': 'Sulabh Mahajan', 'username': 'sulabhM'}

Message: SERVER-33607 Use kV2Unique version for new Unique indexes only
Branch: master
https://github.com/mongodb/mongo/commit/421c1e82b30a14b3bca8e2bf5ef9df2745c5ee7a

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