-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add vector info procedures #4087
Labels
Comments
vga91
added a commit
that referenced
this issue
Jul 11, 2024
vga91
added a commit
that referenced
this issue
Jul 12, 2024
vga91
added a commit
that referenced
this issue
Jul 16, 2024
vga91
added a commit
that referenced
this issue
Jul 30, 2024
vga91
added a commit
that referenced
this issue
Jul 30, 2024
RobertoSannino
pushed a commit
that referenced
this issue
Jul 31, 2024
vga91
added a commit
that referenced
this issue
Dec 4, 2024
vga91
added a commit
that referenced
this issue
Dec 18, 2024
vga91
added a commit
that referenced
this issue
Dec 19, 2024
vga91
added a commit
that referenced
this issue
Jan 15, 2025
vga91
added a commit
that referenced
this issue
Jan 16, 2025
vga91
added a commit
that referenced
this issue
Jan 21, 2025
…d added Milvus and Pinecone support (#4264) * [NOID] Fixes #4087: Add vector info procedures (#4142) * [NOID] Fixes #4080: Add Pinecone and Milvus support (#4088) * [NOID] Fixes #4231: The apoc.vectordb.milvus.query* and apoc.vectordb.weaviate.query* procedures should get the fields config from metadataKey if present (#4241) * Fixes #4231: The apoc.vectordb.milvus.query* and apoc.vectordb.weaviate.query* procedures should get the fields config from metadataKey if present * [NOID] Fixes #4231: The apoc.vectordb.milvus.query* and apoc.vectordb.weaviate.query* procedures should get the fields config from metadataKey if present (#4241) * Fixes #4231: The apoc.vectordb.milvus.query* and apoc.vectordb.weaviate.query* procedures should get the fields config from metadataKey if present
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the vectordb procedures, add a call to an endpoint like this one, to retrieve the collection info.
The procedure names will be e.g "apoc.vectordb.qdrant.info"
The text was updated successfully, but these errors were encountered: