-
Notifications
You must be signed in to change notification settings - Fork 52
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
Consider supporting a reranker model? #301
Comments
Do you have a specific OpenAI doesn't provide a reranker API. I am not too familiar with reranking use case. So please provide as much context and details as possible. |
The reranker model is an important part of RAG (Retrieval-Augmented Generation), and we hope to operate a reranker model (for example, BAAI/bge-reranker-v2-m3) and provide a rerank API. You can refer to the rerank API provided by Cohere: Rerank API. |
Edit: The docs call out that Infinity adheres to Cohere API, which is great. I think maybe that's our shortest route to support reranker models. @michaelfeil what's the API that Infinity provides? https://github.com/michaelfeil/infinity?tab=readme-ov-file#reranking I'm thinking maybe we can re-use Infinity support for adding support for reranker models. |
Reranker API’s don’t have a common ground in their spec. E.g. LiteLLM and I followed Cohere. |
Seems Cohere is also supported in other solutions: https://docs.continue.dev/customize/model-types/reranking I think supporting a Reranker API would be great for fully local private code completion with continue.dev. We support all endpoints (chat completions, code completion, embeddings) except Reranker. |
I'm hopeful that this plan will be put into action. |
It's definitely on the roadmap and I think I have all the info I would need. Right now our focus is on adding support for PVC support and Prefix Cache aware routing. Afterwards we should be able to tackle this. |
No description provided.
The text was updated successfully, but these errors were encountered: