8000 Add support for Embedding Tasks · Issue #58 · wizenheimer/cyyrus · GitHub

More Web Proxy on the site http://driver.im/

Add support for Embedding Tasks #58

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and A4FE privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

1 task

wizenheimer opened this issue Aug 22, 2024 · 0 comments

Assignees

Owner

wizenheimer commented

•

Issue 1

Summary

Wrap LiteLLM to support both Text and Image Embedding Models.

Pain Points

What challenges are users encountering without this feature?

Users may be limited to handling only one type of embedding model, either text or image, which restricts the versatility of their applications.
The lack of unified support for both model types may lead to inefficient workflows and integration issues.

Current Workarounds

Have you come across any alternatives or tried any workarounds?

Users might have to implement separate systems or tools for text and image embeddings, which can be complex and cumbersome.
Custom code might be used to bridge the gap between text and image embeddings, but this could result in inconsistent performance.

Solution

What solution would you like to see?

Wrap LiteLLM to provide seamless support for both text and image embedding models, simplifying integration and enhancing versatility.

References

Have you seen similar solutions or examples elsewhere?

Look into existing frameworks or libraries that offer support for both text and image embeddings for best practices and implementation guidance.

Additional Notes

Is there anything else you’d like us to know?

Integrating support for both embedding types will improve the functionality and usability of LiteLLM.

Contribution

I’d love help with this if needed!

wizenheimer self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

0