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

Remove actualCollection from CollectionUUIDMismatch error response

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution
    • Execution Team 2022-08-22

      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:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: