[8.0 / 8.3] Normalize comparison of CreateCollectionCoordinator documents in terms of collation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • v8.3, v8.0
    • CAR Team 2026-05-11
    • 200
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      With the merge of SERVER-125790 and SERVER-81447 we're now explicitly serializing the collation options used by the _shardsvrCreateCollection command.

      However previous versions passed-through the collation field into the coordinator document, leading to potentially valid retries such as executing the same command to fail. Different options would be used in the stored coordinator document vs the passed-in arguments if the document was created and durably persisted on a newer node version and the retry done on an older node.

      Note that this is purely a UI/UX problem since the actual creation will do the correct thing with the correct options as they are semantically equivalent.

            Assignee:
            Jordi Olivares Provencio
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: