OpenWebUI/docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs synced 2025-06-16 11:28:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #552 from kiettrinhgg/fix/env-qdrant-multitenancy-config-note

Browse Source 
Enhance env-configuration.md for Qdrant Multitenancy mode
This commit is contained in:
Tim Jaeryang Baek 2025-05-20 16:29:34 +04:00 committed by GitHub
commit d6c1c2be71
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/getting-started/env-configuration.md
View File

@ -1210,7 +1210,19 @@ modeling files for reranking.
This will disconect all Qdrant collections created in the previous pattern, which is non-multitenancy. Go to `Admin Settings` > `Documents` > `Reindex Knowledge Base` to migrate existing knowledges.
The Qdrant collections created in the previous pattern will still take resources. Therefore, when you decided to use multitenancy pattern as your default, go to `Admin Settings` > `Documents` to reset Qdrant, which will delete all collections with `open_webui` prefix and then do the Reindex Knowledge Base.
The Qdrant collections created in the previous pattern will still take resources.
Currently, there is no button on the UI for only reset vector DB, if you want to migrate knowledges to multitenancy:
- Remove all collections with `open_webui-knowledge` prefix (or `open_webui` prefix to remove all collections related to Open WebUI) with native Qdrant Client
- Go to `Admin Settings` > `Documents` > `Reindex Knowledge Base` to migrate existing knowledges
`Reindex Knowledge Base` will ONLY migrate knowledges
:::
:::danger
When you decided to use multitenancy pattern as your default and you don't need to migrate old knowledge, go to `Admin Settings` > `Documents` to reset vector and knowledge, which will delete all collections with `open_webui` prefix and knowledges.
:::