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

Don't change index data format version number upon unique index conversions

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Unique index conversions modify the index data format version number to adhere to the versioning scheme. However, nothing actually changes about the data format despite changing the version number. In other words, for secondary indexes, version 6 is already equivalent to version 13 and version 8 is already equivalent to version 14. So, we can simply relax the versioning scheme for secondary indexes and not have to modify the index's version number upon unique conversion.

            Assignee:
            Unassigned Unassigned
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None