Remove actualCollection from CollectionUUIDMismatch error response

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Execution Team 2022-08-22
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently when a CollectionUUIDMismatch error is returned, it contains the name of the collection which corresponds to the provided UUID. However for sharded clusters, the implementation of this was a bit fragile. If we're able, we should consider removing this actualCollection field so that future sharding work does not have to take these edge cases into consideration.

            Assignee:
            Unassigned
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: