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

Test that Query replanning for SBE works only if feature flag is enabled

XMLWordPrintableJSON

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

      1. sbe_pushdown_replan_reason.js checks for the presence of replanReason on the profile entry for SBE cached queries which went through the replanning process.
      2. The suite runs FCV upgrade/downgrade commands, which influence the enabled feature flags
      3. One of those feature flags is featureFlagShardFilteringDistinctScan
        color: Color value is invalid

        , which will make the query use classic instead of SBE due to distinct multiplanning

      color: Color value is invalid

      Starting with SERVER-92456 we use classic instead of sbe when

      {{featureFlagShardFilteringDistinctScan

      color: Color value is invalid

      is enabled.

      }}
       

      color: Color value is invalid

      We should instead only check the presence of the replanReason if the featureFlagShardFilteringDistinctScan is not enable

            Assignee:
            nicola.cabiddu@mongodb.com Nicola Cabiddu
            Reporter:
            nicola.cabiddu@mongodb.com Nicola Cabiddu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: