-
Notifications
You must be signed in to change notification settings - Fork 509
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
feat: Enhance ai-cache Plugin with Vector Similarity-Based LLM Cache Recall and Multi-DB Support #1248
base: main
Are you sure you want to change the base?
Conversation
update update: 注意在使用http协议的时候不要用tls update: add lobechat add: makefile for ai-proxy fix bugs fix bugs fix: redis connection fix: dashvector and dashscope cluster fix: change vdb collection feat: add chroma logic docs: 增加 api 说明 update: no callback version fix: change to callback fix: finish chrome remove: key update: gitignore
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1248 +/- ##
==========================================
+ Coverage 35.91% 43.52% +7.61%
==========================================
Files 69 76 +7
Lines 11576 12320 +744
==========================================
+ Hits 4157 5362 +1205
+ Misses 7104 6622 -482
- Partials 315 336 +21 |
fix: remove key
…to feat/chroma
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
return err | ||
} | ||
|
||
err = d.client.Post( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SaaS 版本的 Weaviate 似乎需要一个 API Key 才能访问。
Ⅰ. Describe what this PR did
This PR extends the functionality of the
ai-cache
plugin, enabling more efficient AI application development by introducing vector similarity-based caching and recall mechanisms.Ⅱ. Does this pull request fix one issue?
Please refer to issue #1040 and #1041.
Ⅲ. Why don't you add test cases (unit test/integration test)?
Test cases will be added later.
Ⅳ. Describe how to verify it
After filling in the
apikey
andChromaCollectionID
indocker-compose-test/envoy.yaml
, execute the following code:cd docker-compose-test/ docker compose up
Then test it by accessing the LLM via cURL:
Ⅴ. Special notes for reviews