Weaviate hybrid fusion: alpha and score gaps change different decisions

Weaviate hybrid fusion combines lexical and vector results, but changing the fusion strategy is not the same intervention as changing alpha. Keep those decisions separate when diagnosing a ranking that overvalues exact words or loses useful semantic evidence.

Distinguish score gaps from positions

The hybrid-search concepts describe relativeScoreFusion and rankedFusion. Relative-score fusion normalizes branch scores while retaining information about their gaps; rank fusion uses positions instead. Equal branch order can therefore produce different final results when score distributions differ. The checked documentation identifies relative-score fusion as the default from version 1.24, but an installed collection or older application can still use an explicitly selected alternative.

Interpret alpha within the chosen method

The hybrid query guide exposes configurable contributions from keyword and vector search. Alpha controls their balance inside the selected setup; it cannot restore a relevant document missing from the candidate inputs. Preserve branch outputs before interpreting a final score. If the lexical branch dominates because it searches an unintended field, adjusting alpha may conceal that schema mistake rather than establish a sensible balance between useful signals.

Keep keyword fields under control

The BM25F query reference documents property selection and weighting. Titles, descriptions and copied navigation text do not necessarily contribute equally useful evidence. Record searchable properties and boosts with the experiment. A field change alters the lexical branch before fusion. Comparing that change against another alpha value without retaining the original branch result makes it impossible to attribute an observed relevance difference.

Test agreement and disagreement

Build a small illustrative fixture with an exact product code, a paraphrased question and a passage whose title matches but body does not answer. Save relevance judgments before tuning. Compare both fusion strategies with identical candidate settings, then investigate alpha independently. The goal is not agreement with a preferred algorithm; it is whether the selected evidence answers the real question.

Change	Hold fixed
Fusion strategy	Branch queries and alpha
Alpha	Strategy and branch configuration
Keyword fields	The prior configuration as a separate control

Inspect explanations before averages

When one query improves and another degrades, examine the branch scores and positions for those documents. An aggregate metric can hide a systematic failure on identifiers or paraphrases. Keep output count and filters unchanged. Do not convert normalized hybrid scores into universal relevance probabilities: their interpretation depends on the retrieval setup and candidate population, and a threshold borrowed from another collection may reject useful evidence.

Preserve the chosen search contract

Retain server/client versions, fusion method, alpha, keyword properties and embedding revision with the held-out fixture. A later default change is not an excuse to silently reinterpret an old result. Recheck the affected branch when its analyzer, document representation or model changes. The useful outcome is a documented combination whose advantages and remaining failure classes are visible, rather than a single magic alpha presented as correct for every corpus.