IndexBuildsCoordinator should always receive an explicit collation

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-04-13, CAR Team 2026-04-27, CAR Team 2026-05-11, CAR Team 2026-05-25, CAR Team 2026-06-08
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Right now, the IndexBuildsCoordinator receives a collation in the storage format, where the absence of a collation is interpreted as a simple collation. This is very error-prone, because in other parts of the system the absence of a collation can instead mean "use the collection's default collation."

      The goal of this ticket is to ensure the collation is always passed explicitly up to the IndexBuildsCoordinator API. The coordinator will then be responsible for converting the specified collation into the storage format.

      This change is important because it removes an ambiguous and fragile convention from a critical path in index creation. By making the collation explicit, we reduce the risk of subtle bugs, ensure consistent behavior across components, and make the code easier to reason about and maintain over time.

       

            Assignee:
            Silvia Surroca
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: