Remove ChromaSingleQueryRetriever #240
Merged
Conversation
This file contains 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
anakin87
approved these changes
Jan 18, 2024
Comment on lines
43
to
44
| if not top_k: | ||
| top_k = 3 |
There was a problem hiding this comment.
unrelated to this PR.
Why not top_k = top_k or self.top_k?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The retriever was originally introduced when Haystack components expected to receive
List[List[Document]], but we lately standardized the format to pass single queries and receive one single list of results. For this reasonChromaSingleQueryRetrieveris being removed andChromaQueryRetrieverchanged so it looks like the other retrievers and can be used as a drop-in replacement in existing pipelines.