Support chat memory based on Elasticsearch #4632
Open
Conversation
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
jiafu1115
changed the title
jiafu1115
force-pushed
the
es
branch
3 times, most recently
from
ec2576c to
d6e073f
Compare
Signed-off-by: stroller <[email protected]>
|
Hi Team: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi Team：
I’ve opened this PR to introduce chat memory support based on Elasticsearch. Elasticsearch's indexes can be archived by time (for example, by week), which makes it a good fit for part of chat memory use cases.
Can anybody help to take a look?
Thanks for review!
BTW: I pasted the integration test result here due to the CI only run the unit test.
