Investigate changes in PM-1942: Allow $changeStream to participate in optimization

    • Type: Epic
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Downstream Change Summary

      Specific downstream impact TBD.

      Description of Linked Ticket

      Epic Summary

      Summary

      $changeStream can participate in optimization resulting in more efficient resource utilization on a single node

      Motivation

      Currently internal $changeStream stages cannot participate in optimization, inhibiting single-node execution performance when the user specifies additional $match / $project pipeline stages.
      In a sharded cluster, user-defined $match and $project stages are not pushed down to shards; can result in excessive network consumption.

      Cast of Characters

      • Product Owner: Katya Kamenieva
      • Project Lead: TBD
      • Program Manager: Craig Homa
      • Drivers Contact: TBD

      Documentation

      Scope Document
      Technical Design Document
      Product Description

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None
              None
              None