Skip to content
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

[Doc] how to support multiple embedding models in different app scenes? #2123

Open
1 of 2 tasks
chuangzhidan opened this issue Nov 12, 2024 · 3 comments
Open
1 of 2 tasks
Labels
documentation Improvements or additions to documentation Waiting for reply

Comments

@chuangzhidan
Copy link

chuangzhidan commented Nov 12, 2024

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

i want to use different embedding models in different scenes, couldn't find it how to do it in ref doc , will u support this function in future?if not,could u tell me where i can change it if i want to change code ? thank u :)

Documentation Links

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
@chuangzhidan chuangzhidan added documentation Improvements or additions to documentation Waiting for reply labels Nov 12, 2024
@Aries-ckt
Copy link
Collaborator

good suggestion, now knowledge space serve support only one embedding model, we will support specifying different embedding models in the knowledge space soon.

@chuangzhidan
Copy link
Author

good suggestion, now knowledge space serve support only one embedding model, we will support specifying different embedding models in the knowledge space soon.

support different scenes such as chat_bi / chat_data /chat_knoledge?

@Aries-ckt
Copy link
Collaborator

Currently, it is true that different applications in the embedding project can only use one embedding model.so we will consider to support different embedding model in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Waiting for reply
Projects
None yet
Development

No branches or pull requests

2 participants