Feat(rerank): Add Cohere Reranker with topN filtering and fallback support #3791
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
This PR introduces a new DocumentPostProcessor implementation that leverages the Cohere Rerank API to reorder retrieved documents based on semantic relevance.
It enables post-retrieval reranking using the Query input and relevance scores returned by the Cohere API.
Key Features
Configuration & Behavior Notes
The rerank feature is only activated when the following properties are present in your configuration
If omitted or disabled, rerank is skipped, and no HTTP calls to Cohere will be made.
Controlling topN Results
If "topN" is not provided in the Query.context() or is invalid, it defaults to 3
Default behavior without topN
Custom topN usage
This ensures the rerank feature remains optional, configurable, and backward-compatible.
Usage Example
Result
Notes