Darragh Jones

I actually get the same error if I use a nullable int without nesting... i.e. ``` ... options.Schema.For().Duplicate(x => x.Altitude); ... [Test] public void BulkInsertAddress() { var docs = new[]...

Actually, in our performance tests we noticed the difference between calling `session.Store(IEnumerable entities)` and using `BulkInsert` was minimal, so we've decided not to use BulkInsert. Therefore we're in no rush...

in my case i'm saving around 5k entities. in my tests this takes around 4 seconds with either approach. however, it seems `bulkinsert` still takes around 4 seconds if i...

I'd also like to be able to inject less than 1 request per second

I am also seeing these errors in the logs. Is there any idea what is actually causing these errors to be logged?

actually my question was more related to the dotnet sdk docs here https://docs.dapr.io/developing-applications/sdks/dotnet/dotnet-client/#invoke-a-service

Any idea when dotnet-monitor will support the new metrics APIs?

Another option is to ditch the dotnet-monitor sidecar and just use the OpenTelemetry to export both your 'system' metrics and application metrics....you just need to add a few additional nuget...

I guess the only example of using the dotnet dapr client to invoke a service is by passing in the app-id. It wasn't clear to me that I can also...

+1