New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for C# SDK v3 #31
Comments
Thanks for the detailed report! They all are great findings 😮 Really appreciate it if you can make the PR. Feel free to reuse some code from #30 if needed. |
For emulator SSL the work-around is covered at https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator#running-on-mac-or-linux |
@asleire regarding the SSL issue, you write that your
Could you explain how you disabled the SSL verification in the client? Thanks a lot! |
@moredatapls |
I'll close this issue since my PR has been merged. I found more issues regarding advanced queries with the C# client, but basic usage works now |
The C# SDK currently does not work with this CosmosDb server.
NuGet package: https://www.nuget.org/packages/Microsoft.Azure.Cosmos/
I discovered the following issues while attempting to make it work:
message
property with non-null value in the response body. Otherwise it will throw a NullReferenceException.queryEngineConfiguration
property is required for querying to work.partitionKeyRanges
is invalid, it ismaxInclusive
but should bemaxExclusive
"True"
value instead of"true"
, causing the server to not handle them as trueA-IM
header. Essentially it expects an etag when retrieving partition keys, and it expects a 302 status code once all keys have been received. Current behavior causes an infinite loop in the C# SDKAfter forking this repo and applying fixes for the above I am able to successfully use this server with the C# SDK.
I noticed you have a current draft PR with some fixes for the Java SDK, which will fix some of the issues here. I can make a PR with the remaining fixes if you'd like
The text was updated successfully, but these errors were encountered: