langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-25 21:47:07 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Is vectordb config mutually exclusive by design #1317

New Issue
Closed
opened 2026-02-21 17:32:12 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:32:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @BorisPolonsky on GitHub (Mar 12, 2024).

Originally assigned to: @takatost on GitHub.

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

Provide a description of the help you need

We are developers of dify-helm and we've received a feature request for enabling multiple vector db simutaneously via .Values.yaml. Our assumption is that only one vectordb (i.e. either weaviate, qdrant or milvus) would be utilized and we've designed our template like this, where environment variables from non-selected vector db won't be added to api or worker for fool proof purpose. Please clarify if it is appropriate specifying environment variables for multiple vector db simutaneously by design.

Originally created by @BorisPolonsky on GitHub (Mar 12, 2024). Originally assigned to: @takatost on GitHub. ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### Provide a description of the help you need We are developers of `dify-helm` and we've received a feature request for enabling multiple vector db **simutaneously** via `.Values.yaml`. Our assumption is that only one vectordb (i.e. either `weaviate`, `qdrant` or `milvus`) would be utilized and we've designed our template like [this](https://github.com/BorisPolonsky/dify-helm/blob/master/charts/dify/templates/config.tpl#L201), where environment variables from non-selected vector db won't be added to `api` or `worker` for fool proof purpose. Please clarify if it is appropriate specifying environment variables for multiple vector db **simutaneously** by design.
yindo closed this issue 2026-02-21 17:32:12 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#1317
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?