Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36547

After 4.2 check_unique_indexes.js shouldn't rely on a specific FCV version

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Execution Team 2019-07-15
    • 50

      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.

            Assignee:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: