Config Ollama chat and Embeddings options via config.toml #601
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rams via the config.toml file
|
Why this is not a thing yet? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is similar to #456, but enables updating of any Ollama parameter exposed by langchain via config. Either PR solves issue #496 and is useful when interfacing with models that demand larger contexts (like deepseek-r1).
It expects the chat options to have a key format matching: https://v03.api.js.langchain.com/interfaces/_langchain_ollama.ChatOllamaInput.html
and the embeddings options to have a key format matching:
https://v03.api.js.langchain.com/interfaces/_langchain_ollama.OllamaEmbeddingsParams.html
I did follow the CONTRIBUTING.md process, tested things and it works well.