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

Extend logic for recognizing used optimizer

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: 7.1 Required
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • Hide

      buildscripts/resmoke.py run -suites=causally_consistent_hedged_reads_jscore_passthrough --continueOnFailure --excludeWithAnyTags=requires_ocsp_stapling,requires_increased_memlock_limits,requires_sbe --jobs=6 --shuffle '-mongodSetParameters={internalQueryFrameworkControl: forceClassicEngine}' --storageEngineCacheSizeGB=1 jstests/core/query/agg_hint.js

      Show
      buildscripts/resmoke.py run - suites=causally_consistent_hedged_reads_jscore_passthrough --continueOnFailure --excludeWithAnyTags=requires_ocsp_stapling,requires_increased_memlock_limits,requires_sbe --jobs=6 --shuffle ' -mongodSetParameters={internalQueryFrameworkControl: forceClassicEngine}' --storageEngineCacheSizeGB=1 jstests/core/query/agg_hint.js
    • 161

      Depending on query and existing failpoints the system may use either classic planner or CQF optimizer. JS tests which assert on explain outputs need to recognize which optimizer has been used to assert correctly.

      The explain helper "usedBonsaiOptimizer" helps with this, however it does not cover all cases. This ticket ensures that the helper treats correctly all explain outputs.

            Assignee:
            matt.olma@mongodb.com Matt Olma
            Reporter:
            matt.olma@mongodb.com Matt Olma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: