Make sure change streams on sharded collections are unversioned and target all shards

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying, Replication, Sharding
    • None
    • Fully Compatible
    • Repl 2017-10-02
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We can't properly target change streams on sharded collections currently (until we have multi-version routing tables), so we should send change streams on sharded collections to all shards and we should opt-out of the shard versioning protocol.

              Assignee:
              Bernard Gorman
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: