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

Investigate why wildcard index candidate plans are non-deterministic

XMLWordPrintableJSON

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

      When working on SERVER-96635, I discovered that running the same wildcard index query multiple times leads to different candidate query plans (different rejected plans in the explain output). 

      Below, I have attached a test, which can be run with the `replica_sets_jscore_pqs_fallback` to  reproduce the scenario.

        1. reproduction_scenario.js
          2 kB

            Assignee:
            steve.tarzia@mongodb.com Steve Tarzia
            Reporter:
            victorfilip.ghita@mongodb.com Victor Ghita
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: