Add metadata filtering capabilities to memory retrieval #20
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
|
@thierrypdamiba I can't see any code changes made by this PR thinking: Could you please verify all the files were committed? |
Update qdrant.py to include changes
|
I can see how that might be helpful. Updated to include the files. |
|
Any plans to merge this? Or is already implemented elsewhere? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
• Support storing memories with arbitrary metadata
• Add metadata filtering in find_memories to filter by metadata fields
• Add configurable result limits for memory retrieval
• Return relevance scores with search results
• Format metadata in search results for better readability