-
Notifications
You must be signed in to change notification settings - Fork 91
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃巸[Provider Request]: Implement Milvus as an Vector DB #1068
Comments
@shabbyjoon, could you please assign this issue to me| |
I would like to work on this issue if possible. |
Hey @shabbyjoon , can I work on this? Previously I have contributed on integrating Zilliz(Milvus Client) to an open source project, I think I can apply the same knowledge here. |
Hi @LuciAkirami! We added a couple more Hacktoberfest tickets for technical contributions, you can check them out here: https://github.com/featureform/featureform/issues Thanks again for your support! :) |
Hi @shabbyjoon James from Milvus community here. glad to talk deeper about the integration and further collaborate and partenership |
And we'd like to the contribution if no one else volunteered |
Description
A Vector Database provider is designed to facilitate nearest-neighbor lookups.
Milvus is a popular open-source vector database that stores, indexes, and manages vector embeddings.
Featureform supports vector databases like Pinecone, Redis, and Weaviate.
In Featureform, Vector DBs share several similarities with an inference store but are distinguished by their support for the client.nearest API. Configuration is typically done when registering an embedding associated with an entity. This setup enables efficient retrieval of nearest neighbors based on feature vectors.
Current Behavior
No response
Desired Behavior
Implement Milvus as a vector database so that it can be registered as a provider in Featureform.
Benefits
With Milvus provider support, users can manage and version their ML embeddings with Featureform while leveraging Milvus's indexing, storage, and nearest neighbor lookups.
Possible Implementation
It should implement the https://github.com/featureform/featureform/blob/main/provider/online.go#L36 interface.
Look at https://github.com/featureform/featureform/blob/main/provider/pinecone.go for inspiration
Additional Context
No response
The text was updated successfully, but these errors were encountered: