Billy Mumby

Hi @henrikkarstrom thanks for this issue we have this on our radar and there is a re-write going on behind the scenes of the in memory repository implementation to try...

Hi @rakeshbimra would you be able to share the full error? Cosmos DB usually logs a JSON body with some more details on the 400 response.

Okay I think @IEvangelist ran into this problem as well a few months back. Have you tried setting the serialised options on `RepositoryOptions` if you see here https://github.com/IEvangelist/azure-cosmos-dotnet-repository/blob/fe87219fd93cd28087f92473e1bafae055f6378f/src/Microsoft.Azure.CosmosRepository/Options/RepositorySerializationOptions.cs#L31 It defaults...

Hey, @mabvanaartrijk I like this idea, so what you are saying is rather than setting the throughput at each level of each container, you would like the throughput at the...

> Hi @mumby0168 . Yes, if you create a new container in the Data Explorer on Azure Portal you have the option to provision dedicated throughput for the container. So...

> Thanks @mumby0168! I've misinterpreted the _SyncAllContainerProperties_ setting. It works perfectly with this setting to false. > > So to recap: manually creating the collections in Data Explorer and setting...

> I'll discuss with my team if we can add it to one of our next sprints👍 Great look forward to hearing from you 👍

Hi @SeanFarrow this has been planned for the paging methods. Not something we've had time to work on yet. I did wrap this myself in an implementation here. This was...

Hi @SeanFarrow we do support this for some of the paging APIs. I think we could start logging this out if that is any help? We do in places but...

Hi @SeanFarrow we would not want to modify the public API surface I do not think. So I don't think either the out parameter or the return type would work...