[SERVER-32991] When V2Unique format indexes are present show a warning message when FCV=4.0 is set Created: 30/Jan/18  Updated: 02/Aug/18  Resolved: 02/Aug/18

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

Type: Improvement Priority: Major - P3
Reporter: Neha Khatri Assignee: Vamsi Boyapati
Resolution: Won't Fix Votes: 0
Labels: nonnyc, storage-engines
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-34489 Enable new format Unique Index via FCV Closed
Sprint: Storage Non-NYC 2018-03-26, Storage Non-NYC 2018-04-09, Storage Engines 2018-07-30, Storage Engines 2018-08-13
Participants:

 Description   

Ensure that when starting up a MongoDB 4.2 binary with FCV=4.0 when V2Unique indexes are present will log a warning message, indicating which indexes are V2Unique format.

Add a test case covering the scenario.



 Comments   
Comment by Alexander Gorrod [ 02/Aug/18 ]

After discussion we can't do this at startup because we don't know the FCV version when opening indexes, and there is only a small amount of value in logging a warning message when downgrading the FCV version - since the requirement is already well documented.

Comment by Alexander Gorrod [ 07/May/18 ]

Guess is 1 days to get it done.

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