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

DocumentSourceSequentialCache can wind up in a suboptimal location due to optimizations

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • ALL

      As part of resharding it came up that during optimizations we may perform optimizations (combining match stages) that cause the placement of the cache to change. Might be worth figuring out a way to place the cache differently before optimizations to block these optimizations.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            ted.tuckman@mongodb.com Ted Tuckman
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: