mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-17 08:21:12 -05:00
[PR #17772] [CLOSED] feat: implement multi-tenancy mode for milvus #24543
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?
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/17772
Author: @Classic298
Created: 9/26/2025
Status: ❌ Closed
Base:
dev← Head:feat/milvus-multitenancy📝 Commits (1)
fd88b0efeat: implement multi-tenancy mode for milvus📊 Changes
5 files changed (+327 additions, -56 deletions)
View changed files
📝
backend/open_webui/config.py(+2 -0)📝
backend/open_webui/retrieval/utils.py(+80 -14)📝
backend/open_webui/retrieval/vector/dbs/milvus.py(+169 -25)📝
backend/open_webui/routers/knowledge.py(+41 -13)📝
backend/open_webui/routers/retrieval.py(+35 -4)📄 Description
This commit introduces a new multi-tenancy mode for the Milvus vector database integration, mirroring the existing architecture for Qdrant. This addresses scalability concerns by preventing the creation of an excessive number of collections.
When
MILVUS_MODEis set tomultitenancy, the system now uses a small set of shared collections (e.g.,knowledge,files) and leverages Milvus partitions to ensure data isolation.Key changes:
MILVUS_MODEandMILVUS_EMBEDDING_DIMENSIONenvironment variables toconfig.py.milvus.pyto pre-create shared collections with partitioning enabled at startup.utils.py.Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:
devbranch.Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.