mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-11 08:22:09 -05:00
[PR #15389] [MERGED] feat: Add qdrant indices #46855
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/15389
Author: @guenhter
Created: 6/29/2025
Status: ✅ Merged
Merged: 6/30/2025
Merged by: @tjbck
Base:
dev← Head:add-qdrant-indices📝 Commits (1)
5c2e0e4feat: add qdrant indices for metadata fields📊 Changes
2 files changed (+38 additions, -0 deletions)
View changed files
📝
backend/open_webui/retrieval/vector/dbs/qdrant.py(+19 -0)📝
backend/open_webui/retrieval/vector/dbs/qdrant_multitenancy.py(+19 -0)📄 Description
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.Changelog Entry
Description
All fieldnames which are part of a query should have an index for performance reasons. This is even enforced on some qdrant cluster like those on qdrant.io, and queries using a unindexed column fail with an error.
Two new indices are crated:
metadata.file_idmetadata.hashThe indices are now created for both the multitenant and non-multitenant qdrant integration.
This change is not affecting existing qdrant collections. Only newline created ones, will get the index.
Changed
metadata.hashandmetadata.file_idfieldsContributor 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.