[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
No issues found with inMemory storage engine. |