Skip to main content

Structured output with Ollama

I talked about Structured Output before in the context of Semantic Kernel. Structured Outputs is a feature that ensures the model will always generate responses that follow a supplied JSON Schema, so you can process the responses in automated fashion without worrying about getting invalid JSON back.

Recently support for Structured Output was announced by Ollama. In this post I want to show you how you can use this in combination with OllamaSharp, the C# client for Ollama.

Using Structured Ouput in OllamaSharp

Remark: Make sure you have latest Ollama version running on your local machine before you continue.

  • Add the OllamaSharp client to your project:

dotnet add package OllamaSharp

  • Now let’s first define our response model:
  • Afterwards we need to initiate a new OllamaSharp client instance:
  • We create a new request object.
    • Notice that we specify a JSON schema object based on the Recipe model we created earlier
  • If we now invoke the application we get a JSON response back in the provided format:

The full example can be found here: wullemsb/SemanticKernelStructuredOutput at OllamaClient

What about using the Semantic Kernel Ollama connector?

At the moment of writing this blog post, I couldn’t get the Structured Output working when combining Semantic Kernel and Ollama.

I explicitly referenced the correct OllamaSharp version:

And used the Ollama connector:

But when calling the api, I still got a response back in an unstructured format:

More information

Semantic Kernel - Structured output

awaescher/OllamaSharp: The easiest way to use the Ollama API in .NET

Support for 'Structured outputs' · awaescher/OllamaSharp · Discussion #152

Structured outputs · Ollama Blog

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more