Unify mongos cursor cache, remove explicit distinction between unsharded and sharded cursors

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Query
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ... since distinguishing between sharded and unsharded collections in mongos is nontrivial and not correct when the sharding status changes. This also interferes with aggregation, since cursor type does not necessarily correspond to input collection sharding state.

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: