📝 docs: Added RAG_USE_FULL_CONTEXT
to .env.example
#4494
Merged
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.
Summary
Currently, there isn't documentation that highlights the ability to use full context of the documents uploaded for RAG. This causes new users like myself to run into subpar RAG results in certain scenarios. Adding the RAG_USE_FULL_CONTEXT to the .env.example file for better visibility.
Relevant PRs
Change Type
Please delete any irrelevant options.
Testing
The functionality of using RAG_USE_FULL_CONTEXT has already existed and been tested. Though, I tested it again and it works. The results of the RAG output visibly includes more context when setting RAG_USE_FULL_CONTEXT=true and not having the variable defined at all in .env. It is more apparent when using smaller models (8b params or less).
Test Configuration:
Checklist
Please delete any irrelevant options.