4.10.3
This bug is straightforward -- the cosmos connector does not work on the new serverless SKU, which is unfortunate.
Steps to reproduce the behavior:
1.Create a serverless Cosmos DB
I expect the library to successfully create containers in the cosmos DB instance.
@dmvtech can you look at this please?
Thanks @don4of4 I'm attempting to reproduce myself. Should be able to confirm tomorrow.
Sounds good. It looks like the issue is just creation, so this should be a straightforward fix.
Yeah, I'm with you on this. Reproduced and in a agreement on very similar to #4310 . I'm assuming if it (options like ContainerThroughput, etc) was nullable, that this would no longer error.
Obviously, you're aware of the workarounds that @EricDahlvang has mentioned in that one, so I won't go into that here.
Thanks for bringing this to our attention.