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

distinct command should pass routingInfo to scatterGather()

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.5.13
    • Component/s: Sharding
    • Query Optimization

      The distinct command orders results according to the collection's default collation if the collection is sharded.

      It obtains the collection's default collation from the routingInfo. However, since scatterGather() internally gets its own copy of routingInfo, the routingInfo used in the command can be for a previous incarnation of the collection (and so have the wrong collection default collation).

      This ticket should make the versioned scatterGather() methods optionally take the routingInfo to use, for commands that need to use the routingInfo themselves for non-routing purposes.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: