Add the with_mongot_extension_fully_enabled suites

XMLWordPrintableJSON

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

      Overview

      Final piece of the per-flag-configuration extension suite families (SERVER-130636 / SERVER-130878 / SERVER-131368): add with_mongot_extension_fully_enabled_* (4 topologies) with every extension feature flag enabled, so $search/$searchMeta, $vectorSearch, and extension stages inside hybrid search all run through the Extensions API.

      Work

      • New extension_flags_fully_enabled / _sharded override blocks (all flags true) and 4 mapping files in buildscripts/resmokeconfig/matrix_suites/; regenerate.
      • Exclusions compose from the existing blocks -- the mapping stacks exclude_incompatible_tests + exclude_search_extension_incompatible + exclude_extensions_inside_hybrid_search_incompatible; no new list needed up front.
      • 4 new Evergreen tasks in the query division tasks.yml (tag-selected by the extensions-secure variants) and burn_in exclusions.
      • Triage via an Evergreen patch: $search-extension + hybrid-extension together is a previously untested combination; some inherited exclusions may be removable and new failures may surface.

      Dependencies

      Stacked last, on SERVER-131368 (the vectorSearch_disabled rename). Once these suites are green, the full 4-family matrix (fully_enabled + one family per disabled flag) is in place.

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

              Created:
              Updated:
              Resolved: