[SERVER-35008] Test unique index upgrade for enterprise storage engines Created: 15/May/18  Updated: 06/Aug/18  Resolved: 06/Aug/18

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

Type: Improvement Priority: Major - P3
Reporter: Alexander Gorrod Assignee: Vamsi Boyapati
Resolution: Done Votes: 0
Labels: nonnyc, storage-engines
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Storage Engines 2018-07-30, Storage Engines 2018-08-13
Participants:

 Description   

We have work in progress to change the format of unique indexes moving forward. That work is specific to the WiredTiger storage engine - in order to support timestamp reads.

Some of the upgrade/downgrade work involves changing data format version (which is internal to the storage engine implementation). Review other enterprise only storage engines, including inMemory to ensure they behave correctly.



 Comments   
Comment by Vamsi Boyapati [ 06/Aug/18 ]

Tested manually as per the scope and hence closing this ticket.

Comment by Vamsi Boyapati [ 03/Aug/18 ]

Tested with --storageEngine inMemory option with evergreen patch : https://evergreen.mongodb.com/version/5b596d752fbabe19728ec6ff

  1. In mongod-latest representing 4.2, inserted docs, created unique index, set fcv to 4.2 and used mongod-4.0 binaries. Behavior is as expected.
  2. In mongod-latest representing 4.2, inserted docs, created unique index, set fcv to 4.0 and used mongod-4.0 binaries. Behavior is as expected.
  3. In mongod-4.0, inserted docs, created unique index, set fcv to 4.0 and used mongod-latest binaries. Behavior is as expected.

No issues found with inMemory storage engine.

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