sthota
1. This occurs when, after the connection has been established, CRUD commands are sent before the authentication command. Note that some MongoDB drivers have a bug where they are not authenticating the connection in rare cases and sending CRUD commands. Could you please check and upgrade to the latest driver of Mongoose/NodeJS-Native/NodeJS-Core driver, which has a rewrite of their client-side auth stack and fixes a lot of bugs. One of such issues is described in https://jira.mongodb.org/browse/NODE-1798 which was fixed by https://github.com/mongodb-js/mongodb-core/commit/7ffb4bbe05...
2. Resource tokens provide fine grained access control but it does require you to implement a custom token management service. We are working on support for Azure AD integration and support for custom roles and policies. The feature is code complete and should be made available soon.
3. Cosmos DB’s SQL query language is supported on a non-relational data model - which maps cleanly to document/column-family/graph. It does not support joins since (unlike a relational model), a single Cosmos container can contain items belonging to any arbitrary schema.
4. Re. API for MongoDB requiring a shard key, we are going to relax this restriction before 7/30/2019. As you noted, we do support an emulator for Windows. We are working on a Linux emulator and should be released later this year.
5. The portal was displaying incorrect cost estimate in certain cases. We addressed it and the fix is being rolled out.
Thank you for the feedback!
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/#Restrictio...
We continue to optimize our indexing layout – there are several key improvements being rolled out. Please share the details of your expensive query ([email protected]) 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!
We continue to optimize our indexing layout – there are several key improvements being rolled out. Please share the details of your expensive query ([email protected]) to help us investigate.
OFFSET/LIMIT (Skip/Take) is currently in private preview. It will be broadly available by 5/15/2019.