3 ms·

We used it also. Ran into the issue that collection (?) names are limited to 64 chars(1) (which wasn't documented anywhere), triggering obscure errors while eve

We used it also. Ran into the issue that collection (?) names are limited to 64 chars(1) (which wasn't documented anywhere), triggering obscure errors while everything was fine from the Azure Frontend. Also even simple queries using an index (and a uniform document structure) cost a comparatively huge amount of RUs compared to a competitor. Icing on the cake was the non-support for paging at that time, and a total fuck-up when we tried a restore from backup operation (which can only be done by calling MS support, no automated way possible). If anyone wants to know details I can provide those. Needless to say we switched to another provider. (1) the names were generated by our automated deployment step, something like {environment}_{product}_{collection-name}

jbreiding 8y ago
Any reason you wouldn't use resource groups and db/collections for segregation instead of encoding into the collection name? I believe all of that hirearchy ends up in the resource URI if you really need it encoded there.
sthota 8y ago
Hi, I am from Cosmos DB engineering team. For SQL API, the collection names have a limit of 255 bytes (we will update the documentation). For Mongo API, we honor the limit prescribed by the API for the combination of <database>.<collection> to be 120 bytes as explained here - https://docs.mongodb.com/manual/reference/limits/#Restriction-on-Collection-Names https://docs.mongodb.com/manual/reference/limits/#Restrictio... We continue to optimize our indexing layout – there are several key improvements being rolled out. Please share the details of your expensive query (askcosmosdb@microsoft.com) to help us investigate. OFFSET/LIMIT (Skip/Take) is currently in private preview. It will be broadly available by 5/15/2019. We are working on customer controlled PITR, which will be available later this year. Thank you for the feedback!

jbreiding 8y ago

Any reason you wouldn't use resource groups and db/collections for segregation instead of encoding into the collection name? I believe all of that hirearchy ends up in the resource URI if you really need it encoded there.

sthota 8y ago

Hi, I am from Cosmos DB engineering team. For SQL API, the collection names have a limit of 255 bytes (we will update the documentation). For Mongo API, we honor the limit prescribed by the API for the combination of <database>.<collection> to be 120 bytes as explained here - https://docs.mongodb.com/manual/reference/limits/#Restriction-on-Collection-Names https://docs.mongodb.com/manual/reference/limits/#Restrictio... We continue to optimize our indexing layout – there are several key improvements being rolled out. Please share the details of your expensive query (askcosmosdb@microsoft.com) to help us investigate. OFFSET/LIMIT (Skip/Take) is currently in private preview. It will be broadly available by 5/15/2019. We are working on customer controlled PITR, which will be available later this year. Thank you for the feedback!