Skip to content
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

Merged
merged 27 commits into from
Oct 27, 2023

Conversation

RichardZhangRZ
Copy link
Contributor

@RichardZhangRZ RichardZhangRZ commented Oct 9, 2023

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 required
  • MILVUS_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 the default database if not provided.
  • MILVUS_TOKEN is the authorization token for the Milvus instance.

Copy link
Contributor

@github-actions github-actions bot left a 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 running git pull and git 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.

@xzdandy
Copy link
Collaborator

xzdandy commented Oct 10, 2023

Hi Richard, thanks for the contribution! What is the status of the pull request?

@RichardZhangRZ RichardZhangRZ changed the title Added Milvus integration for vector create and search Add Milvus integration for vector create and search Oct 10, 2023
@RichardZhangRZ RichardZhangRZ marked this pull request as ready for review October 10, 2023 16:59
evadb/third_party/vector_stores/milvus.py Show resolved Hide resolved
setup.py Show resolved Hide resolved
evadb/third_party/vector_stores/milvus.py Show resolved Hide resolved
@xzdandy xzdandy requested a review from jiashenC October 11, 2023 04:30
@xzdandy xzdandy added Data Sources Features/Bugs related to Data Sources Integrations 🧩 Pull requests that update an integration labels Oct 11, 2023
@xzdandy xzdandy added this to the v0.3.8 milestone Oct 11, 2023
@xzdandy
Copy link
Collaborator

xzdandy commented Oct 17, 2023

Hi @RichardZhangRZ , is this PR ready? Thanks!

@RichardZhangRZ
Copy link
Contributor Author

Hi @RichardZhangRZ , is this PR ready? Thanks!

There are still ongoing conversations, but other than that, the PR should be ready

.circleci/config.yml Outdated Show resolved Hide resolved
Copy link
Collaborator

@xzdandy xzdandy left a 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!

@xzdandy xzdandy modified the milestones: v0.3.8, v0.3.9 Oct 19, 2023
@xzdandy
Copy link
Collaborator

xzdandy commented Oct 20, 2023

We need to address some merging conflicts.

@xzdandy
Copy link
Collaborator

xzdandy commented Oct 24, 2023

The merge does not look correct. I will give it a try.

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
Copy link
Collaborator

@xzdandy xzdandy Oct 24, 2023

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"
Copy link
Collaborator

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.

@xzdandy xzdandy merged commit 71b9aca into georgia-tech-db:staging Oct 27, 2023
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Sources Features/Bugs related to Data Sources Integrations 🧩 Pull requests that update an integration
Projects
Development

Successfully merging this pull request may close these issues.

None yet

4 participants