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

version to 0.5.7 #2610

Merged
merged 1 commit into from
Feb 28, 2024
Merged

version to 0.5.7 #2610

merged 1 commit into from
Feb 28, 2024

Conversation

takatost
Copy link
Collaborator

@takatost takatost commented Feb 28, 2024

Description

Vector Database Migrate Tool

When you want to switch to another vector database, you can deactivate or delete the original vector database after switching.

How to use

Step:

  1. If you are starting from local source code, modify the environment variable in the .env file to the vector database you want to migrate to.
    For example:
VECTOR_STORE=qdrant
  1. If you are starting from docker compose, modify the environment variable in the docker-compose.yaml file to the vector database you want to migrate to, both api and worker are all needed.

For example:

# The type of vector store to use. Supported values are `weaviate`, `qdrant`, `milvus`.
VECTOR_STORE: qdrant
  1. run the below command in your terminal or docker container
flask vdb-migrarte

Type of Change

  • Version release

@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Feb 28, 2024
@takatost takatost merged commit 5bd3b02 into main Feb 28, 2024
10 checks passed
@takatost takatost deleted the feat/bump-0-5-7 branch February 28, 2024 10:07
HuberyHuV1 pushed a commit to HuberyHuV1/dify that referenced this pull request Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:S This PR changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant