[SERVER-32757] Resolve any fallout due IndexVersion bump in mongodb Created: 18/Jan/18  Updated: 25/Feb/18  Resolved: 25/Feb/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: Sulabh Mahajan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-32825 Add the infrastructure for upgrade/do... Closed
Sprint: Storage 2018-02-26
Participants:

 Description   

There will be a new IndexDescriptor::IndexVersion flag of kV2Unique. However the IndexDescriptor::IndexVersion field applies across storage engines. A change in the IndexVersion field opens up possibilities of breaking non-unique indexes and indexes in other storage engines.
Resolve any such issues encountered due to the update in IndexVersion.



 Comments   
Comment by Sulabh Mahajan [ 25/Feb/18 ]

I tested with code change for SERVER-33415 and new index enabled and found two issues. I have created tickets SERVER-33458 and SERVER-33459 for them.
I am closing this ticket and continuing work with those two tickets.

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