Qdrant Hybrid Search Combining

QdrantOfficialPublished by Qdrant

Skill
Tool integration
Data and AI
Apache-2.0
No issues found

From the author

Fusing scores from multiple searches into a single ranked result (RRF, DBSF, custom fusion). Use when someone asks 'RRF or DBSF?', 'how to combine sparse and dense', 'how to combine scores from multiple searches?', 'custom fusion', 'fusion is not producing good results', 'how do I tune RRF', 'what k should I use', or 'how do I set fusion weights'

— the description by Qdrant

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This guide provides best practices for combining ranked candidate lists from parallel search prefetches. It covers standard fusion methods like Reciprocal Rank Fusion (RRF) and Distribution-Based Score Fusion (DBSF), as well as advanced custom fusion techniques using formula queries. The content emphasizes the importance of empirical tuning over arbitrary weight selection and provides a structured approach to optimizing hybrid search performance.

What it does

Explains how to use RRF for rank-based fusion when scores are on incomparable scales.
Details the use of DBSF for normalizing score distributions before fusion.
Provides instructions for implementing custom fusion logic using formula queries and payload metadata.
Outlines a systematic tuning order for RRF parameters and weights.
Describes advanced fusion techniques using vector representations and late interaction models.
Lists common pitfalls to avoid when configuring hybrid search pipelines.

When to use it

When you need to combine results from multiple search strategies like BM25 and dense embeddings.
When you need to incorporate payload metadata like recency or popularity into your ranking.
When default fusion settings are not producing optimal search relevance.
When you need to tune fusion parameters based on specific dataset characteristics.
When you are ready to trade compute resources for higher precision ranking.

Advantages

Provides a clear, prioritized workflow for tuning hybrid search.
Offers multiple approaches ranging from simple rank-based fusion to complex custom formulas.
Includes specific guidance on handling score distributions and normalization.
Helps avoid common mistakes like using linear weighted fusion on incomparable scales.

Usage examples

“How do I combine sparse and dense search results?”: The guide recommends starting with RRF for incomparable scales or DBSF for normalized score distributions, emphasizing comparative testing on your own labels.
“How do I tune RRF parameters?”: It suggests settling on a k value first, then sweeping weights at that k, and validating the results on held-out queries.
“Can I use payload fields in my fusion logic?”: Yes, you can use formula queries to access both prefetch scores and payload field values to implement custom ranking logic.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/qdrant/qdrant-hybrid-search-combining/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip qdrant-hybrid-search-combining.zip -d .agents/skills

Documentation by Qdrant

Combining Prefetch Results

The outer query fuses ranked candidate lists from all parallel prefetches into one ranked list of results. Fusion methods differ in whether they use rank, score or directly vector representations of candidates (their similarity to the outer query) and whether final score incorporates payload metadata. All methods support flat (one fusion step) and nested (multi-stage) prefetch structures.

Tune in this order, cheapest first: confirm fusion beats each prefetch alone on your labels, compare Qdrant's default RRF vs DBSF, if tuning RRF: settle k, then sweep weights at that k, and validate on held-out queries. A weight pair is only valid for the k it was tuned with Tune in this order

Scores Are Not Comparable Across Prefetches & You Want Some Easy Baseline

Use when: searches produce scores on different scales, like BM25 and cosine on dense embeddings.

RRF

RRF (Reciprocal Rank Fusion): rank-based, ignores scores magnitude.
Start with RRF at Qdrant's defaults, k=2 and equal weights.
Tune k to control rank sensitivity in RRF fusion, choosing the value from your labels Use labels to choose a k range.
Add per-prefetch weights when one search should dominate, using Weighted RRF. Weights should be customized per collection and retrievers' score distributions. Tune weights last.

DBSF

DBSF (Distribution-Based Score Fusion): normalizes score distributions per prefetch before fusing them, for that, instead of min-max, uses mean +- 3 deviations on prefetched list of scores. Avoid relying on resulting absolute scores, as scores in DBSF are normalized per prefetch (aka per a retrieved list of search results), and might be uncomparable across queries.
DBSF has no parameters to tune, so compare it before hand-tuning RRF k and weights. Confirm on your own labels Compare RRF and DBSF on your labels

Need Custom Fusion

Use when: recency, popularity or other payload values should affect the merged ranking alongside candidate scores or you need a custom fusion.

With formula query, access score of each prefetch and, if desired, payload field values.

If you want to implement custom fusion on score of each prefetch:

Use decay or any other available expressions for normalizing score distributions before fusing them.
Parameters of these expressions should be based on the collection & retriever score distributions (for example, adjusting these parameters on a subsample of real queries).
Formula query is unable to provide ranks for custom fusions

When using FormulaQuery over multiple prefetches (e.g. per-representation weighting):

$score[i] indexes prefetches in declaration order. Reordering the prefetch= list silently shifts which weight applies to which retriever.
Provide defaults for every $score[i] so the formula still evaluates for candidates that surfaced from only a subset of prefetches.
On Qdrant 1.19.1 or newer, max and min expressions take the best or worst of several $score[i] (for example, keep each point's best score across per-field BM25 prefetches), cap a boost (min(cap, boost)), or clamp a value with max(lo, min(hi, x)). A point absent from a prefetch has $score[i] of 0.0, which wins max over negative scores and min over positive ones, so set defaults (keys include the $, placed beside formula, never inside it) to a value outside the expected score range such as -1e30 for max or 1e30 for min Max and min.
On 1.19.1 or newer, acosh supports exact geodesic-distance rescoring for hyperbolic embeddings (Lorentz model with Dot distance, acosh(-$score), negated so closest ranks first). The input must be at least 1 Hyperbolic distance.
Start with RRF when scores are on incomparable scales (e.g. BM25 + cosine). Reach for FormulaQuery only when explicit per-representation weighting or payload-driven boosts are required, and normalize each $score[i] (decay or min-max on a sampled distribution) before combining linearly.

Need Good Ranking of Fused Candidates and Ready To Spend More Resources

Use when: you want to use similarity between query and candidates' vector representations as the prefetches combiner and simultaneously ranker. More resource heavy than score/rank based fusions, but might be necessary due to use case requirements or need in a high top-K precision of results (when parallel prefetches have overall a good recall of retrieved candidates).

More candidates only help if the ranker can use them. Deeper prefetches can raise the best possible score

You can use any type of vector as an outer query over the prefetches, to perform the fusion on the server-side in one QueryAPI request: sparse, dense, multivector. For that, same type of vector representations for documents need to be stored as named vectors per point.

Instead of using client-side fusion through cross-encoders, a popular option is Late interaction models-based fusion, through reranking on multivectors (e.g. ColBERT for text, ColPali and ColQwen for images).

Most precise but highest compute/resource usage.
Configure multivectors used for fusion through reranking with HNSW disabled like in Hybrid Search with Reranking tutorial.

What NOT to Do

Use linear weighted fusion on incomparable score ranges. Why not.
Use "vibe" defined weights in weighted RRF. Weights should be fine-tuned per dataset and retrieval pipelines.
Pick any fusion type without comparative experiments.
Use late interaction multivectors for fusion without evaluating cheaper analogues, for example, MUVERA. More in multi-vector Qdrant search course

Files

ATTRIBUTION.mdAdded by AutoGineer914 B
LICENSELicence file added by AutoGineer11.1 KiB
SKILL.md7.4 KiB

LICENSE

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright 2026 Qdrant Solutions GmbH

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by

Qdrant

Publisher

Qdrant (Official)

Source

qdrant/skills · skills/qdrant-search-quality/search-strategies/hybrid-search/combining-searches · commit 9f55f6a

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-08

AutoGineer is not affiliated with or endorsed by Qdrant.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download qdrant-hybrid-search-combining.zip