mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 02:48:13 -05:00
[PR #6050] [MERGED] feat: add qdrant vector db connector #37447
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/6050
Author: @RobinBially
Created: 10/9/2024
Status: ✅ Merged
Merged: 10/9/2024
Merged by: @tjbck
Base:
dev← Head:main📝 Commits (6)
878a570add qdrant as vector dbb185524Merge branch 'open-webui:main' into mainb56f77eimprovements2c59f2dfix critical bug54dc943improvements34150fcadd NO_LIMIT var📊 Changes
4 files changed (+184 additions, -0 deletions)
View changed files
📝
backend/open_webui/apps/retrieval/vector/connector.py(+4 -0)➕
backend/open_webui/apps/retrieval/vector/dbs/qdrant.py(+176 -0)📝
backend/open_webui/config.py(+3 -0)📝
backend/requirements.txt(+1 -0)📄 Description
Changelog
Added
Changed
Note to first-time contributors
Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Pull Request Checklist
Additional Information
This pull request introduces support for Qdrant as a vector database client and enhances the overall flexibility of vector database usage in the project. These changes bring several benefits:
Increased Database Options: By adding Qdrant support and allowing for more vector databases, users can choose the best option for their specific use case, improving overall system adaptability.
Performance Optimization: The groundwork for storing sparse vectors will enable future performance improvements, especially when querying large knowledge bases.
Future-proofing: This implementation makes it easier to integrate new vector database solutions as they emerge, keeping the project up-to-date with the latest technologies.
Customization: Users can now tailor their vector database choice to their specific requirements, such as speed, storage capacity, or specific feature sets.
This pull request aims to enhance the vector database capabilities of the application, providing more options and laying the groundwork for future optimizations. If there are any questions or further clarifications needed, please let me know. Thank you for reviewing and considering these changes.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.