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

Check data format version compatibility when converting index to non-unique

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2025-02-17, Storage Execution 2025-03-03, Storage Execution 2025-03-17, Storage Execution 2025-03-31, Storage Execution 2025-04-14
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Non-unique indexes require the record id to be part of the key rather than part of the value, as shown in this table. However, when converting a unique index to be non-unique via the forceNonUnique parameter of collMod, currently the data format is not checked for compatibility.

      If we do this, we may also want to think about the current naming of the command parameter since it includes "force" which would no longer be accurate.

            Assignee:
            yuhong.zhang@mongodb.com Yuhong Zhang
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None