[SERVER-36547] After 4.2 check_unique_indexes.js shouldn't rely on a specific FCV version Created: 09/Aug/18 Updated: 10/Jul/19 Resolved: 10/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sulabh Mahajan | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | open_todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Execution Team 2019-07-15 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 50 | ||||||||||||
| Description |
|
In 4.2 release unique indexes got an upgrade and their internal wiredtiger specific version changed accordingly. check_unique_indexes.js currently checks for the unique indexes to have the correct versions but relies on obtaining current FCV and comparing it to statically coded "4.2" in the script. Once we are past 4.2, we can just assert that we have the correct versions, there wont be a need to check for the FCV. This ticket is filed to update check_unique_indexes.js after 4.2 to do the same. |
| Comments |
| Comment by Xiangyu Yao (Inactive) [ 10/Jul/19 ] |
|
Closing this ticket and merge the code changes into |
| Comment by Githook User [ 10/Jul/19 ] |
|
Author: {'name': 'Xiangyu Yao', 'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com'}Message: Revert " This reverts commit 264994554c4e298fb151386f33251d171bbbb613. |
| Comment by Githook User [ 05/Jul/19 ] |
|
Author: {'name': 'Xiangyu Yao', 'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com'}Message: |