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

make ClusterClientCursorParams::RemoteCursor store the ShardId

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.7
    • Affects Version/s: 3.5.6
    • Component/s: Querying, Sharding
    • None
    • Fully Compatible
    • Sharding 2017-05-08

      This is prep work for replacing ClusterAggregate's use of Strategy::commandOp() with establishCursors().

      This is because aggregation may need to know which shard a cursor resides on, in order to select a merging shard from the shards involved in the aggregation.

      Note david.storch charlie.swanson, it seems plausible to choose any shard to do the merging, not just one that had a cursor established on it. Is it actually necessary to choose one that had a cursor established on it?

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: