-
Notifications
You must be signed in to change notification settings - Fork 16.1k
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
[draft]: propagate score through retriever #20800
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
query: str, | ||
*, | ||
run_manager: CallbackManagerForRetrieverRun, | ||
include_score: bool = False, | ||
) -> List[Document]: | ||
if self.search_type == "similarity": |
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.
this case feels like it could lead to some confusion. Should we throw an error if include_score
is set to true in this case with a message to switch search type?
Also do we want to use relevance scores for this, or do we want to just return raw scores? My goal was to deprecate the relevance score stuff as-is in #20302
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.
Might also be good to add a typing override such that when include_score
is set to true, this returns DocumentSearchHit
. Alternative is to just add the score stuff as an optional to Document
.
No description provided.