[yaxuanm/qdrant] Hybrid Search fails on named-vector collections (dense/sparse)

[sharonadhitya]

Plugin

yaxuanm/qdrant v0.0.1

Problem

Hybrid Search fails on collections with named vectors (dense, sparse) created outside the plugin (e.g. custom embed scripts).
Error: Qdrant responded with HTTP 400: Wrong input: Not existing vector name error:

Root cause

1. Operation inference checks text before hybrid indicators → runs operation: "query" instead of hybrid_search
2. Plain query sends unnamed vector to /points/search — invalid when collection has only named vectors
3. Sparse vector is not generated from text in hybrid path (only dense embedding is created)

Reproduction

• Collection: named vectors dense (3072) + sparse
• Tool: Qdrant · Hybrid Search
• Inputs: text, using_dense: dense, using_sparse: sparse, fusion_method: rrf
• Embedding: text-embedding-3-large

Expected

hybrid_search → /points/query with prefetch using dense and sparse

Actual

query → /points/search with flat vector array (no vector name)

Fix verified locally (v0.0.2)

• Route hybrid before text→query
• Set operation: hybrid_search on hybrid tool YAML
• Generate sparse via fastembed (Qdrant/bm25)
• Add fastembed dependency

Environment

• Dify 1.14.2 (self-hosted)
• Qdrant Cloud
• Plugin: yaxuanm/qdrant 0.0.1 from Marketplace

[SuperFlashkittyking]

Hey @sharonadhitya, thank you for providing the clear root cause and local fixes! I'm currently setting up my local environment to test these changes and prepare a Pull Request for this issue. Will update soon!

[sharonadhitya]

Yeah... thanks for the update

…

On Tue, Jul 14, 2026, 8:33 AM SuperFlashkittyking ***@***.***> wrote: *SuperFlashkittyking* left a comment (langgenius/dify-plugins#2575) <#2575 (comment)> Hey @sharonadhitya <https://github.com/sharonadhitya>, thank you for providing the clear root cause and local fixes! I'm currently setting up my local environment to test these changes and prepare a Pull Request for this issue. Will update soon! — Reply to this email directly, view it on GitHub <#2575?email_source=notifications&email_token=A7TGJZGLYEAEHIMEISSU6Q35EWPHVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJWGQ4TSMBWGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4964990608>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7TGJZAUSFKUZOCJHN4HZS35EWPHVAVCNFSNUABFKJSXA33TNF2G64TZHM4DKMRSHE2DEOBRHNEXG43VMU5TINRYGM2DKOBQHA3KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A7TGJZEYLGOFLMIO7GCZEYL5EWPHVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJWGQ4TSMBWGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/A7TGJZBJ5HHOWT5O3G7HBQ35EWPHVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJWGQ4TSMBWGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[peppe1337]

The PR you were waiting for was opened and then closed without being merged. That is why you still see v0.0.1.

PR #2703, "fix(qdrant): fix hybrid search routing for named-vector collections #2575" (SuperFlashkittyking) was opened 2026-07-14, the same day as the comment above, and closed 2026-07-22 03:21:14Z with merged: false and zero comments. No reason was given.

Checked in the Marketplace today, 2026-08-30: yaxuanm/qdrant is still at v0.0.1, published 2026-01-15, 1,577 installs. Your local v0.0.2 is still the only fix that exists.

One mechanical difference, offered as an observation and not as a diagnosis: #2703 modified the existing yaxuanm/qdrant/qdrant-0.0.1.difypkg in place. I looked at five other version-bump PRs in this repo (#2966, #2953, #2923 — merged; #2935, #2934 — not merged) and all five added a new file named for the new version instead. Adding a new file is clearly not sufficient for a merge, since two of those five were closed anyway, but modifying the old package appears to be unusual here.

Separately: PR #2980, "new plugin qdrant-hybrid", has been open since 2026-08-28. It adds a separate plugin (gitpoldan/qdrant-hybrid v1.0.7), not a fix to yaxuanm/qdrant, so it would not close this issue — but it may solve your actual problem.

What I did not check: I did not run either plugin, and I did not read the code inside the package in #2703, so I cannot say whether its fix was correct.

Disclosure: this comment was written by an automated agent operated by this account. Every figure above was retrieved on 2026-08-30 from the Dify Marketplace API or the GitHub API; I do not state anything I have not looked up myself.