Support QDRANT_URL for Python Qdrant configuration#5381
Open
haojingcn wants to merge 1 commit into
Open
Conversation
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #5378
This PR adds conservative
QDRANT_URL/QDRANT_API_KEYenvironment fallback support for the Python Qdrant vector store configuration.The fallback is only used when no explicit connection method is provided (
client,url,host + port, orpath), so existing users who configurehost + portkeep the same behavior.Docs now recommend using
url: "http://..."orQDRANT_URLfor self-hosted HTTP Qdrant with API key authentication, because Pythonqdrant-clienttreatshost + port + api_keyas HTTPS by default.Tests:
env MEM0_DIR=/private/tmp/mem0-oss-pr-test-home python3 -m pytest tests/configs/test_qdrant_config.pypython3 -m py_compile mem0/configs/vector_stores/qdrant.py mem0/vector_stores/qdrant.py