-
I want to support multi chatbot with single langserve routes statement.
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 8 replies
-
The way to do this now is via configurable runnables chain.invoke(..., {'configurable': {'chatbot_name': 'name1'}) I'll expose the underlying API handler in a bit to give users more freedom to do custom things like path parameters (but with a bit more effort too) |
Beta Was this translation helpful? Give feedback.
-
For reference here are configurable chain examples: |
Beta Was this translation helpful? Give feedback.
-
There are some problems with the configuration at runtime:
|
Beta Was this translation helpful? Give feedback.
-
Hi @kientv , sorry missed the extra questions here! The underlying API Handler has complete flexibility: With that you can define path parameters.
Will check but I suspect it's not due to run time configuration. The root cause of almost all streaming problems is that one or more runnables used in the chain do not provide support streaming.
This is not likely to be caused by run time configuration. You'll need to provide more context for me to be able to help with response time of vectorstores.
The attached examples are examples that show how to use configurable runnables, they need to be adapted for your use case. What's your use case? Are you doing chat over your docs with vectorstores? Or is the goal to keep track of chat history (in which case you need a backend to store the chat history). |
Beta Was this translation helpful? Give feedback.
It's an abstract method so you need to leave some implementation in place even if it's not used: