AdminAzure Cosmos DB Team
(Admin, Microsoft Azure)
My feedback
-
1,518 votes
We have just released a major update to our pricing for Cosmos DB.
Starting today, customers can now provision a database with just 400 RU/s (or about $ 0.77/day USD). Combined with the ability to share throughput across collections this should make Cosmos DB much more affordable to users with many small collections
We invite you to checkout our new pricing in the Azure Portal and give us feedback.
Thank you for your patience and feedback.
-
109 votes
More details on Azure Cosmos DB on Azure Stack will follow as we make progress on it.
Thanks for the feedback.
We are still reviewing this as there are a number of dependencies and teams involved. We will update the status here as this progresses.
Thanks.
-
3,632 votes
This feature is currently in active development. We will update this item to complete once it has shipped so those voting/commenting should get notified.
Thank you everyone for your patience.
We can't give an exact date but this is actively being worked on now and expect soon.
Thanks!
At this time, I can say we are working on some foundational pieces which will light up skip/take in future.
-
1 vote
Thanks, for bringing it up. We will address this ASAP.
-
70 votes
For this we recommend using Azure Search. This is not on our roadmap. If that ever changes we will reopen this item.
Thanks.
Pretty much all of $text functionality (and more) has been implemented in Azure Search and we're happy to let you know that it now supports for MongoDB API collections (in private preview). Working with MongoDB collections is very similar to working with SQL Cosmos DB collections as described in https://docs.microsoft.com/azure/search/search-howto-index-cosmosdb
To create a MongoDB datasource, POST an HTTP request as shown below:
POST https://[service name].search.windows.net/datasources?api-version=2016-09-01
Content-Type: application/json
api-key: [Search service admin key]
{
"name": "mymongodbdatasource",
"type": "documentdb",
"credentials": {
"connectionString": "AccountEndpoint=https://<Your Cosmos DB account name>.documents.azure.com;AccountKey=<Your Cosmos DB account key>;Database=<Your database>;ApiKind=MongoDb"
},
"container": { "name": "<Your collection>", "query": null },
"dataChangeDetectionPolicy": {
"@odata.type": "#Microsoft.Azure.Search.HighWaterMarkChangeDetectionPolicy",
"highWaterMarkColumnName": "_ts"
}
}Note:
1. Use `documentdb` as the data source type.
2. Do not use a MongoDB connection string that you would use in your MongoDB application. Instead, construct the connection string as shown above. Make sure to add **ApiKind=MongoDb** to the connection string.Once you've created the data source, follow the steps in https://docs.microsoft.com/azure/search/search-howto-index-cosmosdb to create a search index, create an indexer, and monitor the indexer execution.
## Known issues and limitations
1. Only the REST API is supported. For now, you cannot create or edit MongdoDB data sources using Azure Portal or Azure Search .NET SDK. However, you **can** monitor execution history of MongoDB indexers in the portal.
2. Custom queries are not supported: `container.query` parameter must be set to null or omitted. If you need to use a custom query, please let us know at the emails below.
If you encounter any issues, please contact azscustquestions@microsoft.com
Currently, simple text search is provided through $regex operator. More comprehensive text search is coming shortly through Azure Search that will be able to index MongoDB API collections as well: https://feedback.azure.com/forums/263029-azure-search/suggestions/18861421-documentdb-indexer-should-be-able-to-index-mongodb
-
54 votes
We are currently working on this feature and have made it available in Preview in the Azure Portal.
Please feel free to test Aggregation Pipeline support for your MongoDB API accounts in Cosmos DB by opening your MongoDB API account, then clicking on “Preview” tab on left hand side and then Enable for Aggregation Pipeline.
While there please feel free to test support for MongoDB 3.4 support as well as Per-Document TTL support.
Thank you for your request and votes.
We are implementing a number of changes in aggregation pipeline this quarter. Some of the results will bee seen in both speed and RU charges by the end of April 2018.
replaceRoot support is on our roadmap. The workaround currently is to use simple $project: { _id:0, "<document_root>":1 } stage instead. It will give pretty much same results, except that it will include the name of the field used as a new document_root as well, which you can filter out (or simply omit) on the client side.
-
651 votes
We are actively working on this feature. We will update this item when this feature ships so you will receive an update.
Thank you for your feedback.
[UPDATE] Support for positional operator is expected to be released around April 2018
-
1 vote
This work is currently under way. Will update here as this moves towards general availability.
Thank you for your suggestion and votes.
Currently, projection definition only supports "1" to include the field in projection (as per https://docs.mongodb.com/manual/tutorial/project-fields-from-query-results/#return-the-specified-fields-and-the-id-field-only)
As a workaround, can you try the following command
Command: db.getCollection('Employee').find({ "FullName": /User/i}).projection({ "FullName" : 1 })
@Dominic, The new minimum level for databases is 400 RU/s. It is no longer 10,000 RU/s.