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

XMLWordPrintableJSON

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

      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 (Inactive)
            Reporter:
            Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: