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

Can we upgrade the Weaviate component? #13397

New Issue
Closed
opened 2026-02-21 19:11:59 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 19:11:59 -05:00
Owner
Copy Link
Copy Source

Originally created by @MrXionGe on GitHub (Apr 26, 2025).

Originally assigned to: @JohnJyong 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I checked the latest docker-compose files (v1.3.0 and v0.15.6). The weaviate components are both v1.19.0.

In the new version, Weaviate fixed a lot of bugs and added some features. Should we consider upgrading Weaviate?

Or, is there any other reason why we should keep v1.19.0?

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @MrXionGe on GitHub (Apr 26, 2025). Originally assigned to: @JohnJyong 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I checked the latest docker-compose files (v1.3.0 and v0.15.6). The weaviate components are both v1.19.0. In the new version, Weaviate fixed a lot of bugs and added some features. Should we consider upgrading Weaviate? Or, is there any other reason why we should keep v1.19.0? ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 👻 feat:ragstale labels 2026-02-21 19:11:59 -05:00
yindo closed this issue 2026-02-21 19:11:59 -05:00
yindo commented 2026-02-21 19:11:59 -05:00
Author
Owner
Copy Link
Copy Source

@MrXionGe commented on GitHub (Apr 26, 2025):

If possible, I can change the Weaviate version in the self-hosted service. But I'm also worried that there might be compatibility issues.

@MrXionGe commented on GitHub (Apr 26, 2025): If possible, I can change the Weaviate version in the self-hosted service. But I'm also worried that there might be compatibility issues.
yindo commented 2026-02-21 19:11:59 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 26, 2025):

I have checked with @JohnJyong , we do have a plan to support higher version of weaviate. However we do not have time to do it in recent feature. We still needs some time to check and verify if the higher version won't have breaking changes to existing data.

@crazywoola commented on GitHub (Apr 26, 2025): I have checked with @JohnJyong , we do have a plan to support higher version of weaviate. However we do not have time to do it in recent feature. We still needs some time to check and verify if the higher version won't have breaking changes to existing data.
yindo commented 2026-02-21 19:11:59 -05:00
Author
Owner
Copy Link
Copy Source

@MrXionGe commented on GitHub (Apr 26, 2025):

@crazywoola If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate?

@MrXionGe commented on GitHub (Apr 26, 2025): @crazywoola If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate?
yindo commented 2026-02-21 19:12:00 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 27, 2025):

@crazywoola If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate?

Afaik, it will break some existing features, like metadata and knowledge retrieval.

@crazywoola commented on GitHub (Apr 27, 2025): > [@crazywoola](https://github.com/crazywoola) If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate? Afaik, it will break some existing features, like metadata and knowledge retrieval.
yindo commented 2026-02-21 19:12:00 -05:00
Author
Owner
Copy Link
Copy Source

@MrXionGe commented on GitHub (Apr 27, 2025):

Afaik, it will break some existing features, like metadata and knowledge retrieval.

Got it. I'd better be more cautious.

@MrXionGe commented on GitHub (Apr 27, 2025): > > Afaik, it will break some existing features, like metadata and knowledge retrieval. Got it. I'd better be more cautious.
yindo commented 2026-02-21 19:12:00 -05:00
Author
Owner
Copy Link
Copy Source

@dc-vin commented on GitHub (Apr 29, 2025):

@crazywoola If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate?

Afaik, it will break some existing features, like metadata and knowledge retrieval.

May I ask if I can directly use the latest version when deploying in a brand - new environment? I'd like to try the new version of the vector database to see if it will perform better in retrieval accuracy.

@dc-vin commented on GitHub (Apr 29, 2025): > > [@crazywoola](https://github.com/crazywoola) If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate? > > Afaik, it will break some existing features, like metadata and knowledge retrieval. May I ask if I can directly use the latest version when deploying in a brand - new environment? I'd like to try the new version of the vector database to see if it will perform better in retrieval accuracy.
yindo commented 2026-02-21 19:12:00 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 29, 2025):

@crazywoola If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate?

Afaik, it will break some existing features, like metadata and knowledge retrieval.

May I ask if I can directly use the latest version when deploying in a brand - new environment? I'd like to try the new version of the vector database to see if it will perform better in retrieval accuracy.

Yes, actually you can do this.

@crazywoola commented on GitHub (Apr 29, 2025): > > > [@crazywoola](https://github.com/crazywoola) If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate? > > > > > > Afaik, it will break some existing features, like metadata and knowledge retrieval. > > May I ask if I can directly use the latest version when deploying in a brand - new environment? I'd like to try the new version of the vector database to see if it will perform better in retrieval accuracy. Yes, actually you can do this.
yindo commented 2026-02-21 19:12:00 -05:00
Author
Owner
Copy Link
Copy Source

@dc-vin commented on GitHub (Apr 29, 2025):

@crazywoola If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate?

Afaik, it will break some existing features, like metadata and knowledge retrieval.

May I ask if I can directly use the latest version when deploying in a brand - new environment? I'd like to try the new version of the vector database to see if it will perform better in retrieval accuracy.

Yes, actually you can do this.

Thank you. I will give it a try to see the effect.

@dc-vin commented on GitHub (Apr 29, 2025): > > > > [@crazywoola](https://github.com/crazywoola) If I'm planning to start a completely new self-hosted service, can I use a higher version of weaviate? > > > > > > > > > Afaik, it will break some existing features, like metadata and knowledge retrieval. > > > > > > May I ask if I can directly use the latest version when deploying in a brand - new environment? I'd like to try the new version of the vector database to see if it will perform better in retrieval accuracy. > > Yes, actually you can do this. Thank you. I will give it a try to see the effect.
yindo commented 2026-02-21 19:12:00 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 29, 2025):

Hi, @MrXionGe. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You suggested upgrading the Weaviate component from version 1.19.0 in the docker-compose files to access bug fixes and new features.
  • The maintainer confirmed plans to support newer Weaviate versions but highlighted no immediate timeline due to the need to ensure no breaking changes to existing data.
  • It was noted that using a higher Weaviate version in a new self-hosted deployment is possible but may break some features like metadata and knowledge retrieval.
  • Another user mentioned testing the latest Weaviate version in a new deployment to evaluate retrieval performance.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 29, 2025): Hi, @MrXionGe. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You suggested upgrading the Weaviate component from version 1.19.0 in the docker-compose files to access bug fixes and new features. - The maintainer confirmed plans to support newer Weaviate versions but highlighted no immediate timeline due to the need to ensure no breaking changes to existing data. - It was noted that using a higher Weaviate version in a new self-hosted deployment is possible but may break some features like metadata and knowledge retrieval. - Another user mentioned testing the latest Weaviate version in a new deployment to evaluate retrieval performance. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 stale 👻 feat:rag
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#13397
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?