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 #557 from mecattaf/patch-2
Some checks failed
Deploy site to Pages / build (push) Has been cancelled
Details
Deploy site to Pages / deploy (push) Has been cancelled
Details

Browse Source 
docs: grammar and clarity fixes for multitenancy/Qdrant section (foll…
This commit is contained in:
Tim Jaeryang Baek 2025-05-22 15:25:44 +04:00 committed by GitHub
commit 6b64fdd35b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1209,19 +1209,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.
The Qdrant collections created in the previous pattern will still consume 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
Currently, there is no button in the UI to only reset the vector DB. If you want to migrate knowledge to multitenancy:
- Remove all collections with the `open_webui-knowledge` prefix (or `open_webui` prefix to remove all collections related to Open WebUI) using the native Qdrant client
- Go to `Admin Settings` > `Documents` > `Reindex Knowledge Base` to migrate existing knowledge base
`Reindex Knowledge Base` will ONLY migrate knowledges
`Reindex Knowledge Base` will ONLY migrate the knowledge base
:::
:::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.
If you decide to use the 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 the `open_webui` prefix and all stored knowledge.
:::