From 9fdbc4e40d25be901a3b20ff4358351047fed627 Mon Sep 17 00:00:00 2001 From: Classic298 <27028174+Classic298@users.noreply.github.com> Date: Mon, 29 Sep 2025 11:31:47 +0200 Subject: [PATCH 1/3] Update env-configuration.mdx --- docs/getting-started/env-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/env-configuration.mdx b/docs/getting-started/env-configuration.mdx index 60e3c218..002ca168 100644 --- a/docs/getting-started/env-configuration.mdx +++ b/docs/getting-started/env-configuration.mdx @@ -1367,7 +1367,7 @@ After successful migration (from milvus to multitenancy milvus), legacy collecti ::: -:::danger +:::warning **Critical Considerations** From 0a84df68aec76378f6373ae4d75a71c4a554b3af Mon Sep 17 00:00:00 2001 From: Classic298 <27028174+Classic298@users.noreply.github.com> Date: Mon, 29 Sep 2025 12:34:46 +0200 Subject: [PATCH 2/3] fix --- docs/getting-started/env-configuration.mdx | 22 +++++++--------------- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/docs/getting-started/env-configuration.mdx b/docs/getting-started/env-configuration.mdx index 002ca168..60bce345 100644 --- a/docs/getting-started/env-configuration.mdx +++ b/docs/getting-started/env-configuration.mdx @@ -1314,7 +1314,6 @@ pip install open-webui[all] - Description: Enables multitenancy pattern for Milvus collections management, which significantly reduces RAM usage and computational overhead by consolidating similar vector data structures. Controls whether Milvus uses multitenancy collection architecture. When enabled, all vector data is consolidated into 5 shared collections (memories, knowledge, files, web_search, hash_based) instead of creating individual collections per resource. Data isolation is achieved via a resource_id field rather than collection-level separation. :::info - **Benefits of multitenancy mode:** - Significantly reduced RAM consumption (5 collections vs potentially hundreds) - Lower computational overhead from collection management @@ -1323,19 +1322,16 @@ pip install open-webui[all] **Technical implementation:** -- All memories go into {prefix}_memories -- All knowledge bases go into {prefix}_knowledge -- All uploaded files go into {prefix}_files -- Web search results go into {prefix}_web_search -- Hash-based collections go into {prefix}_hash_based +- All memories go into `{prefix}_memories` +- All knowledge bases go into `{prefix}_knowledge` +- All uploaded files go into `{prefix}_files` +- Web search results go into `{prefix}_web_search` +- Hash-based collections go into `{prefix}_hash_based` - Each entry includes a resource_id field matching the original collection name - Queries automatically filter by resource_id to maintain data isolation - ::: -:::info - -**Migration from Legacy Mode to Multitenancy** +:::info **Migration from Legacy Mode to Multitenancy** **What happens when you enable multitenancy when you already have a normal milvus database with data in it:** - Existing collections (pattern: open_webui_{collection_name}) remain in Milvus but **become inaccessible** to Open WebUI @@ -1364,12 +1360,9 @@ After successful migration (from milvus to multitenancy milvus), legacy collecti - No one-click "migrate and cleanup" button exists - Vector DB reset from UI (Admin Settings > Documents > Reset Vector Storage/Knowledge) only affects the active mode's collections - Legacy collections require manual cleanup via Milvus client tools - ::: -:::warning - -**Critical Considerations** +:::warning **Critical Considerations** **Before enabling multitenancy on an existing installation:** - Data loss risk: File vectors and user memory vectors are NOT migrated automatically. Only knowledge base content can be reindexed (migrated). @@ -1393,7 +1386,6 @@ After successful migration (from milvus to multitenancy milvus), legacy collecti - Set `ENABLE_MILVUS_MULTITENANCY_MODE=true` - Restart Open WebUI - Re-upload/re-create knowledge bases from scratch - ::: #### `MILVUS_COLLECTION_PREFIX` From 5ca69901c240f436e39b90ce3eb9f51112b893f5 Mon Sep 17 00:00:00 2001 From: Classic298 <27028174+Classic298@users.noreply.github.com> Date: Mon, 29 Sep 2025 12:39:05 +0200 Subject: [PATCH 3/3] Update env-configuration.mdx --- docs/getting-started/env-configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/env-configuration.mdx b/docs/getting-started/env-configuration.mdx index 60bce345..24e042fb 100644 --- a/docs/getting-started/env-configuration.mdx +++ b/docs/getting-started/env-configuration.mdx @@ -1334,7 +1334,7 @@ pip install open-webui[all] :::info **Migration from Legacy Mode to Multitenancy** **What happens when you enable multitenancy when you already have a normal milvus database with data in it:** -- Existing collections (pattern: open_webui_{collection_name}) remain in Milvus but **become inaccessible** to Open WebUI +- Existing collections (pattern: `open_webui_{collection_name}`) remain in Milvus but **become inaccessible** to Open WebUI - New data is written to the 5 shared multitenancy collections - Application treats knowledge bases as empty until reindexed - Files and memories are NOT automatically migrated to the new collection schema and will appear missing