Handle edge cases for deprioritizing unbounded user collection scans

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Workload Scheduling
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As of SERVER-72440 we execute unbounded user collection scans with low storage admission priority. However there are some edge cases where we may end up deprioritizing a scan which isn't actually unbounded. For instance the following pipeline:

      [{$unwind: "$foo"}, {$limit: 10}]
      

      Such a query isn't particularly useful as it uses a limit without a sort, so we accepted this limitation for the time being. But it would be good to go through the remaining edge cases so that the behavior is consistent.

              Assignee:
              Unassigned
              Reporter:
              Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: