-
Notifications
You must be signed in to change notification settings - Fork 263
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 Milvus integration for vector create and search #1269
Add Milvus integration for vector create and search #1269
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👋 Hello @RichardZhangRZ, thanks for submitting a EVA DB PR 🙏 To allow your work to be integrated as seamlessly as possible, we advise you to:
- ✅ Verify that your PR is up-to-date with
georgia-tech-db/eva
master
branch. If your PR is behind you can update your code by clicking the 'Update branch' button or by runninggit pull
andgit merge master
locally. - ✅ Verify that all EVA DB Continuous Integration (CI) checks are passing.
- ✅ Reduce changes to the absolute minimum required for your bug fix or feature addition.
Hi Richard, thanks for the contribution! What is the status of the pull request? |
Hi @RichardZhangRZ , is this PR ready? Thanks! |
There are still ongoing conversations, but other than that, the PR should be ready |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Richard! Very nice PR!
We need to address some merging conflicts. |
ec8146a
to
410361b
Compare
The merge does not look correct. I will give it a try. |
.circleci/config.yml
Outdated
else | ||
pip install ".[dev,pinecone,chromadb]" # ray < 2.5.0 does not work with python 3.11 ray-project/ray#33864 | ||
pip install ".[dev,pinecone,chromadb,milvus]" # ray < 2.5.0 does not work with python 3.11 ray-project/ray#33864 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove milvus
since we are not running any test.
* `MILVUS_DB_NAME` is the name of the database to be used. This will default to the `default` database if not provided. | ||
* `MILVUS_TOKEN` is the authorization token for the Milvus instance. | ||
|
||
The above values can either be set in the evadb.yml config file, or in the os environment fields "MILVUS_URI", "MILVUS_USER", "MILVUS_PASSWORD", "MILVUS_DB_NAME", and "MILVUS_TOKEN" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use SET
command is the way to do it now. Example: SET MILVUS_URI = 'http://localhost:19530;'
. We no longer have evadb.yml file. OS environment is not recommended, since it does not work in a client-server setup.
Integrated Milvus vector store into EvaDB. Added a
MilvusVectorStore
class and Milvus type for query parsing and execution.Below are environment values for the use of the Milvus index:
MILVUS_URI
is the URI of the Milvus instance (which would be http://localhost:19530 when running locally). This value is requiredMILVUS_USER
is the name of the user for the Milvus instance.MILVUS_PASSWORD
is the password of the user for the Milvus instance.MILVUS_DB_NAME
is the name of the database to be used. This will default to thedefault
database if not provided.MILVUS_TOKEN
is the authorization token for the Milvus instance.