From 078019c1597a56f4d2d4052f7ba308d77bd9635d Mon Sep 17 00:00:00 2001 From: Kiet Trinh Date: Mon, 19 May 2025 07:51:10 +0000 Subject: [PATCH] Enhance env-configuration.md with detailed instructions for migrating to multitenancy in Qdrant. Added steps for removing old collections and clarified the reindexing process for existing knowledge. --- docs/getting-started/env-configuration.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/getting-started/env-configuration.md b/docs/getting-started/env-configuration.md index 21398dd..faa6200 100644 --- a/docs/getting-started/env-configuration.md +++ b/docs/getting-started/env-configuration.md @@ -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. :::