-
Notifications
You must be signed in to change notification settings - Fork 98
Adding retriever specification to _search API #2551
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
Conversation
Running
|
I wouldn't worry about those, as you mention they are not related to your changes. Given that |
Thanks @carlosdelest ! AFAICT there are no new validation errors introduced with these changes, as I'll mark it for review and we can take it from there. :) |
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.
Overall looks good, I've left a few suggestions to make sure we get the field type right.
Can you check about the RRF Retriever field being optional ? I hav en't found anything that goes in that direction but I may have missed something.
Do you mean the |
Thanks for taking a look @Anaethelion ! I've pushed some changes as per your suggestions :) |
… k and num_candidates to integers in knn interfaces
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
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.
LGTM!
(cherry picked from commit 370532a)
This PR adds the
retriever
specification to the_search
API, as is also defined in the 8.14.0 documentation to be released here .Closes #2508