Investigate using SBE in all cases where multiplanning doesn't generate a distinct scan

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We should look into whether we can do something better than validating distinct eligibility twice (see SERVER-93694), e.g. falling back to classic only in cases where distinct multiplanning actually generates a DISTINCT_SCAN, and otherwise using SBE if we can.

              Assignee:
              Daniel Segel
              Reporter:
              Alya Berciu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: