[SERVER-32990] Make sure that V2Unique indexes operate correctly after downgrade using MongoDB 4.2 binaries Created: 30/Jan/18 Updated: 06/Dec/22 Resolved: 07/May/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: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Sprint: | Storage Non-NYC 2018-03-26, Storage Non-NYC 2018-04-09 | ||||||||
| Participants: | |||||||||
| Description |
|
When a database that has been operating with FCV=4.2 is downgraded to FCV=4.0, it should continue to operate. Ensure that:
This may not require a code change but is worthwhile to test. |