mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #15197] feat: Qdrant Support for RAG #33025
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tdiprima on GitHub (Jun 21, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15197
Check Existing Issues
Problem Description
Hey all — they said Qdrant isn't officially supported per #6386, but the docs suggest otherwise. Qdrant is listed as a supported vector database.
The related Qdrant-specific variables like
QDRANT_API_KEY,QDRANT_URI, andENABLE_QDRANT_MULTITENANCY_MODEalso show Open WebUI has some infrastructure for it, but the following error suggests it's not fully functional.I've got Qdrant running fine outside of WebUI, but trying to add documents throws:
400: 'NoneType' object has no attribute 'collection_exists'.ChromaDB just isn't cutting it for RAG — it's way too slow once you scale past a few hundred docs. Qdrant could seriously improve performance here. Would love to see better support and clearer error handling around this. Happy to help test. 🙏
Desired Solution you'd like
Qdrant should play nicely with Open WebUI.
Alternatives Considered
A faster vector database should be the default database.
Additional Context
Using ChromaDB for RAG? You ask a question, then wait a full minute and a half just to start getting a response. Then it trickles out... one. word. at. a. time. with long pauses in between — while your fan spins up like a jet engine about to take off. 🛫
@tdiprima commented on GitHub (Jun 21, 2025):
Just saw #10008 mentioning Open WebUI creating a collection per document, which could hurt performance at scale (e.g., ~1400 files crashing). Enabling
ENABLE_QDRANT_MULTITENANCY_MODEmight help consolidate collections. Could this be addressed alongside better Qdrant support? Happy to test any fixes!@tjbck commented on GitHub (Jun 25, 2025):
PR Welcome, Qdrant is 100% managed by external contributions.
@guenhter commented on GitHub (Jun 26, 2025):
@tdiprima what issue do you have? We also use qdrant with
ENABLE_QDRANT_MULTITENANCY_MODEturned on, and it works fine for us.@tdiprima commented on GitHub (Jun 27, 2025):
@guenhter Thanks for jumping in! Here's the main issue I'm hitting:
Qdrant is running fine outside Open WebUI, but when I try to add documents through the UI, I get this error:
From what I can tell, it's choking on a call that assumes a collection manager exists but returns
None. This happens even withENABLE_QDRANT_MULTITENANCY_MODE=true.Would it help if I shared my
docker-compose.yml? I'm happy to post it if that’ll shed more light.Also, I saw in #10008 that Open WebUI might be making a new Qdrant collection per file, which would wreck performance at scale (I've got >1400 files). Are you doing anything custom to consolidate collections or batch uploads?
Appreciate any insight — I really want to get Qdrant working as a drop-in upgrade from ChromaDB, especially for larger datasets.
@guenhter commented on GitHub (Jun 27, 2025):
We don't do anything special. This is how my compose looks like:
Even if
ENABLE_QDRANT_MULTITENANCY_MODE=true, this works@tdiprima commented on GitHub (Jun 27, 2025):
@guenhter Thanks for that! It's working now! 😅
@guenhter commented on GitHub (Jun 27, 2025):
Out of curiosity: What was the issue with your config?
@tdiprima commented on GitHub (Jun 27, 2025):
I had
QDRANT_URLinstead ofQDRANT_URI. Fixed that, and added aQDRANT_API_KEYfor good measure.