Enable featureFlagExtensionsInsideHybridSearch in the with_mongot_extension suites

XMLWordPrintableJSON

    • Query Integration
    • Fully Compatible
    • v9.0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Overview

      As part of the move to per-flag-configuration suite families (see SERVER-130636), this ticket adds with_mongot_extension_search_disabled_* (4 topologies): every extension feature flag enabled except featureFlagSearchExtension – legacy $search running alongside extension $vectorSearch and extension hybrid search. Enabled now that the mongot-extension (v2.0.2+) and the IFR-kickback fix (SERVER-130918) have landed.

      Work

      • New extension_flags_search_disabled override blocks and 4 mapping files under buildscripts/resmokeconfig/matrix_suites/; regenerated suites. Mappings stack the shared exclude_incompatible_tests block plus the new exclude_extensions_inside_hybrid_search_incompatible delta block (SERVER-131307/131308).
      • 4 new Evergreen tasks in the query division tasks.yml (tag-selected by the extensions-secure variants)
      • burn_in exclusions for the new suites
      • hybrid_search_on_search_view.js accepts either error code for the view-incompatibility ban

      Related

      • SERVER-130636: hybridSearch_disabled family
      • Follow-up tickets (TBD): rename the legacy suites to vectorSearch_disabled; add fully_enabled last

      Acceptance criteria

      All 4 new tasks green on the extensions-secure variants.

            Assignee:
            Will Buerger
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: