Tripwire 10535800: extension $vectorSearch in $scoreFusion input reports no score metadata on sharded

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the with_mongot_extension_* sharded suites (single_shard, sharded_collections, sharded_cluster), a $scoreFusion whose input pipeline is an extension $vectorSearch crashes with tripwire assertion 10535800 (document_source_score_fusion.cpp:109):

      "The metadata dependency tracker determined $scoreFusion input pipeline does not generate score metadata, despite the input pipeline stages being previously validated as such."

      The tassert is pipeline->generatesMetadataType(DocumentMetadataFields::kScore). LiteParsedScoreFusion::validate() asserts the input pipeline produces score metadata, but the fully-parsed pipeline disagrees on sharded topologies (it agrees on single node, where the same tests pass). featureFlagExtensionsInsideHybridSearch is OFF.

      Affects any $scoreFusion + $vectorSearch pipeline on sharded. Surfaced by re-enabling tests under SERVER-131001; these are excluded on sharded only pending this fix:
      - jstests/with_mongot/e2e/hybridSearch/score_fusion_lookup.js
      - jstests/with_mongot/e2e/hybridSearch/hybrid_search_weights_test.js

      Repro: run either test in with_mongot_extension_single_shard. Single-node passes.

      Verified via Evergreen patch 6a514c65032630000750776c: single_node green; all 3 sharded tasks fail with tripwire 10535800.

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

              Created:
              Updated:
              Resolved: