-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Add query_vector_builder Support to Diversify Retriever
#139094
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
Merged
markjhoy
merged 9 commits into
elastic:main
from
markjhoy:markjhoy/add_query_vector_builder_support_diversify_retriever
Dec 8, 2025
+382
−63
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a9aef94
Add query_vector_builder support to diversify
markjhoy fad45ae
Merge branch 'main' into markjhoy/add_query_vector_builder_support_di…
markjhoy 693a432
add docs; rewrite tests; cleanups
markjhoy 17c1081
Merge branch 'main' into markjhoy/add_query_vector_builder_support_di…
markjhoy 9ccb78c
context - return null if no query vector
markjhoy d69af11
add yaml test to verify use query_vector_builder
markjhoy 94eb716
Merge branch 'main' into markjhoy/add_query_vector_builder_support_di…
markjhoy 62ef3af
rename YAML test; validate builder; cleanups
markjhoy 050624b
Merge branch 'main' into markjhoy/add_query_vector_builder_support_di…
markjhoy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Please don't throw 🍅 at me 🙈
I think we should verify that we want the same
query_vector_builderAPI here. There's some legacy API crust, for example the API asks for amodel_idetc. and there's opportunity to modernize it withinference_id. This would be more work, though, so I'm not raising it as a blocker to the PR more as a discussion if that's something we want to bite off or if this is OK.If we decide to go forward with
query_vector_builder, perhaps not for this PR but the docs could use a bit of work here to define allowed parameters, and have something directly linkable.Uh oh!
There was an error while loading. Please reload this page.
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.
I agree with what you're saying - but I think it's a larger, and more discrete PR (as it also touches other users of the QueryVectorBuilder). The docs however are probably a good idea.
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.
Agreed, it can be a followup
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.
I'll add a task for this.