Ollama connector #770
Merged
Ollama connector #770
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation and Context (Why the change? What's the scenario?)
Although Ollama service protocol seemingly follows OpenAI behavior, Azure Open AI/OpenAI/SK OpenAI C# connectors are not fully functional when pointed to Ollama service, leading to various errors.
This PR introduces a new connector dedicated to Ollama, allowing to use it for Text Generation and Text Embedding generation.
The Ollama connector can be used for service and serverless mode. The PR includes an example (212), I've also manually tested the service with the new connector, using "phi3:medium-128k" and "nomic-embed-text" on Apple Silicon.
High level description (Approach, Design)