fix:duplicate cache keys caused by concurrent write and cache_value field type problem#4
Merged
longbingljw merged 13 commits intooceanbase:dify-for-mysqlfrom Jul 17, 2025
longbingljw:cache-test
Merged
fix:duplicate cache keys caused by concurrent write and cache_value field type problem#4longbingljw merged 13 commits intooceanbase:dify-for-mysqlfrom longbingljw:cache-test
longbingljw merged 13 commits intooceanbase:dify-for-mysqlfrom
longbingljw:cache-test
Conversation
added 13 commits
July 11, 2025 17:25
…e cache keys caused by concurrent writes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix the issue of duplicate cache keys caused by concurrent writes after replacing Redis support with MySQL cache, change the cache_value field type from blob to longblob, and use a mirror source to accelerate the image building process.
Solution Description