Separating infinity server capability from reranking capability #506
Replies: 1 comment 2 replies
-
@noamgershi Understandable. This feature request is already fully implemented and documented. Also multiple docs and in the readme there is docs on this!
I want to use infinity from python. This is also possible. The pip package is modular.
Lastly I am happy you submit this request, but not excited of the underlying message of: I do not want to contribute x I also don't want to contribute analytics x I did not check the docs x please add and maintain another package. I saw this is the first issue opening in Github. It would be grateful to see an adoption of a oss mindset and contributing back! I'll move this to discussions, hopefully it hints more people to the public docs that have similar requests (which is reasonable). |
Beta Was this translation helpful? Give feedback.
-
Feature request
Hi
I want to suggest that this repo will be separated to its reranking-feature and its fastAPI server-feature, and its reranking-feature will be in a separate pypi dependency (other then infinity_emb).
I would like to be able to get a pypi dependency which contains only the reranking/embedding/etc features, but without the fastAPI server feature.
Meaning - only the content of file engine.py, and I will create the AsyncEmbeddingEngine and I will call the rerank() method directly, without having the infinity_server.py file at all.
Motivation
Basically I don't want features like the sending StartupTelemetry to PostHog at all, and also I want to be able to have control on the server creation/parameters
Your contribution
Not currently
Beta Was this translation helpful? Give feedback.
All reactions