[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: |
|
||||||||
| 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. |
| Comments |
| Comment by Sulabh Mahajan [ 25/Feb/18 ] |
|
I tested with code change for |