azure-cosmosdb

问题 It is mentioned in most of the articles that if we are using Cosmos Db and newly creating our app we should go with Cosmos db sql api . Mongo api and cassandra api can be used when u already have your app integrated with actual mongo and cassandra and we want to migrate quickly to cosmosdb and not change the ecosystem. But when we create a new cluster of cosmosdb in azure it ask for api type. That means internally there must be some storage differences and internal engine processing

问题 We are using Cosmos DB SQL API and here's a collection XYZ with: Size: Unlimited Throughput: 50000 RU/s PartitionKey: Hashed We are inserting 200,000 records each of size ~2.1 KB and having same value for a partition key column. Per our knowledge all the docs with same partition key value are stored in the same logical partition, and a logical partition should not exceed 10 GB limit whether we are on fixed or unlimited sized collection. Clearly our total data is not even 0.5 GB. However, in

问题 I can see there is support for offset/limit when accessing a Cosmos DB in Azure via the SQL API - but does OData support this yet? 回答1: UPDATE You can download my demo in github. And this article and offical document can help u. Data in My Storage account Test by postman TestDataController.cs public class TestDataController : ODataController { [EnableQuery] public IHttpActionResult Get() { CloudStorageAccount account = CloudStorageAccount.Parse("DefaultEndpointsProtocol=***x=core.windows.net"

问题 i'm a newbie in Mongo and Cosmos DB. I'm trying to get some random values from one collection with the following aggregation query, but it delivers repeatedly same result: db.jokes.aggregate( [ { $sample: { size: 1 } } ] ) Operation consumed 2.39 RUs { "_id" : ObjectId("5b1526501e39b24ccc50d369"), "joke" : "Giraffes are born or created when Chuck Norris uppercuts a Horse!", "language" : "en" } db.jokes.aggregate( [ { $sample: { size: 1 } } ] ) Operation consumed 2.39 RUs { "_id" : ObjectId(

问题 In the scenario where we have 1000 entries (unique keys) entering cosmos per minute, is it safe to use /id as the partition key? In particular, there is the concept of Logical Partitions https://docs.microsoft.com/en-us/azure/cosmos-db/partition-data The graphic here scares me a little bit, showing that the logical partitions are actual entities (Ex. "city": "London"). If I have an 8 hour TTL and 1000 entries per minute, I don't necessarily want 480,000 logical partitions that cosmos needs to

问题 In the scenario where we have 1000 entries (unique keys) entering cosmos per minute, is it safe to use /id as the partition key? In particular, there is the concept of Logical Partitions https://docs.microsoft.com/en-us/azure/cosmos-db/partition-data The graphic here scares me a little bit, showing that the logical partitions are actual entities (Ex. "city": "London"). If I have an 8 hour TTL and 1000 entries per minute, I don't necessarily want 480,000 logical partitions that cosmos needs to

问题 I'm setting up a Chatbot with the Microsoft Bot Framework and Azure. I want to save my "UserState" in a database in order to easily analyze the user data. I managed to save my userState in form of JSON documents in Azure Cosmos DB. The problem is that each interaction with the bot creates a new "document" in a "collection" in Cosmos DB. How can I easily merge the data (data structure is consistent) and in the best case have the data in some kind of table? The tool I want to use for analyzing

问题 I'm setting up a Chatbot with the Microsoft Bot Framework and Azure. I want to save my "UserState" in a database in order to easily analyze the user data. I managed to save my userState in form of JSON documents in Azure Cosmos DB. The problem is that each interaction with the bot creates a new "document" in a "collection" in Cosmos DB. How can I easily merge the data (data structure is consistent) and in the best case have the data in some kind of table? The tool I want to use for analyzing

问题 Multi-Master Database with single region: SDK reports ~10 RU to perform a write operation Multi-Master Database with 5 regions: : SDK reports ~46.86 RU for the same operation (~5x to incorporate replication to all regions. Makes sense) If you have a collection provisioned at 10k RU, does cosmos provision 10k RU for every region? The microsoft docs would suggest so but then the SDK reports all region cost when writing to the local region as above which seems a bit odd / confusing? Additionally

问题 I'm new to CosmosDb and azure blob storage, as a requirement I need to reference a file uploaded to azure blob storage from a document in CosmosDb and use it in the attachment section to save the metadata. I know the json metadata stucture should be like this: { "id":"image13d65101-90c4-4c2a-a423-fbf221c73233", "contentType":"image/jpg", "media":"www.bing.com", "_rid":"rnYYAMVFUAUBAAAAAAAAAEC+LNM=", "_ts":1408056025, "_self":"dbs\/rnYYAA==\/colls\/rnYYAMVFUAU=\/docs\/rnYYAMVFUAUBAAAAAAAAAA==\