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

Support rolling upgrade to new unique index format

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.3
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage 2018-02-26, Storage Non-NYC 2018-03-12

      We are adding a new unique index format to support secondary apply with timestamps. The new format will remain compatible with the old format. This ticket encapsulates adding support for inserting into indexes created in the old format:

      • Create a test that populates a unique index in the old format, then switches to the new format and starts inserting data. (Don’t try to hook up FCV yet - that comes later, so another mechanism will be required in local testing).
      • Have the insert/update path identify when an old-version entry exists and remove it, prior to doing an insert.
      • There should be no additional work to support secondaries, but they should be tested at this stage.

            Assignee:
            neha.khatri Neha Khatri
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: