Chat memory implementation for Neo4j #2063
Closed
Conversation
This file contains 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
added 9 commits
January 15, 2025 14:06
Signed-off-by: Enrico Rampazzo <[email protected]>
Signed-off-by: Enrico Rampazzo <[email protected]>
Signed-off-by: Enrico Rampazzo <[email protected]>
Signed-off-by: Enrico Rampazzo <[email protected]>
…feature/neo4j-chat-memory
|
Sorry @ilayaperumalg , I will close and reopen this PR after signing all the commits correctly |
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.
I followed the Cassandra implementation as a guide. As you can see, this implementation supports all the
MessageTypes defined by Spring AI. At the moment, there's no TTL support for messages, unlike in Cassandra's implementation.The common
initialize-schemaparameter is also unsupported, as this implementation, at least at the moment, does not create any index or constraint.