feat: add metadata inspection tools for Agent document store filtering#11620
Closed
sarthakraghuvanshi wants to merge 1 commit into
Closed
feat: add metadata inspection tools for Agent document store filtering#11620sarthakraghuvanshi wants to merge 1 commit into
sarthakraghuvanshi wants to merge 1 commit into
Conversation
Agents using retrieval pipelines had no way to discover what metadata fields exist in a document store or what values they hold, so filters could not be offered as an option at runtime. This adds three new Tool subclasses that wrap the existing metadata-inspection methods on DocumentStore implementations: - ListMetadataFieldsTool – returns all metadata fields and their types - GetMetadataFieldValuesTool – returns distinct values for a field - GetMetadataFieldRangeTool – returns min/max for a numeric field Also extends the DocumentStore Protocol with the three corresponding method signatures so type-checking works against any compliant store, and exports all three classes from haystack.tools. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sarthakraghuvanshi
requested review from
anakin87
and removed request for
a team
|
Someone is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
|
Sarthak seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Contributor
|
Closing as explained in this comment #11000 (comment) |
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
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.
Agents using retrieval pipelines had no way to discover what metadata fields exist in a document store or what values they hold, so filters could not be offered as an option at runtime. This adds three new Tool subclasses that wrap the existing metadata-inspection methods on DocumentStore implementations:
Also extends the DocumentStore Protocol with the three corresponding method signatures so type-checking works against any compliant store, and exports all three classes from haystack.tools.
Related Issues
Proposed Changes:
How did you test it?
Notes for the reviewer
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.