Preserved custom keys in RetrievalQA #6647
Closed
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.
Description
Currently
RetrievalQA
drops any extra keys in the prompt apart from the memory and user input. So if I want a prompt like this:Here
context
is retrieved from the database,history
comes from memory andquery
is the last input provided by the user. If some extra context has to be provided apart from conversation history and database, likeextra_context1
andextra_context2
,RetrievalQA
cannot currently handle it.With this change one can simply provide extra keys in in the
.run()
function ofRetrievalQA
. Like so:Maintainer
@rlancemartin