azure-cosmosdb

问题 I have the following code running in an Azure Function (V2); new DocumentClient(new Uri(keys.dbEndPoint), keys.dbPrimaryKey); Which has worked fine running in azure functions on localhost until today, without changing anything I'm now getting the following exception: Data [IDictionary]:{System.Collections.ListDictionaryInternal} HResult [int]:-2146233036 HelpLink [string]:null InnerException [Exception]:{System.NullReferenceException: Object reference not set to an instance of an object.}

问题 We use Cosmo DB as "MongoDB" , We have a database that is only 45MB in size, less than 10,000 documents across all collections. We run light queries and writes each day, less than 3000 requests/day, also we run “MongoDB Dump” each night to dump the entire database to local server for backup, as said, the downloaded file is only around 45 MB, so I presume it is not too big. In Feb 2018, we received a bill which is around £3,500 which is surprisingly ridiculous. it looks like we were being

问题 I have a Azure Function with a CosmosDBTrigger working on a consumption play monitored with Application Insights. The collection being monitored has 500,000 inserts in the change feed. The consumption plan scales up the number of instances to 15 within a few minutes but only the first instance is able to process any changes. I assume this is because of the lease is kept by the first instance. I am essentially paying for 14 instances to do nothing. I noticed you are supposed to be able to set

问题 I tried to create a stored procedure using the sample sp creation code from Azure docs, but i couldn't fetch the collection details. It always returns null. Stored Procedure // SAMPLE STORED PROCEDURE function sample(prefix) { var collection = getContext().getCollection(); console.log(JSON.stringify(collection)); // Query documents and take 1st item. var isAccepted = collection.queryDocuments( collection.getSelfLink(), 'SELECT * FROM root r', function (err, feed, options) { if (err) throw err

问题 I have an Excel file that originally had about 200 rows, and I was able to convert the excel file to a data table and everything got inserted into the documentdb correctly. The Excel file now has 5000 rows and it is not inserting after 30-40 records insertion and rest of all the rows are not inserted into the documentdb I found some exception as below. Microsoft.Azure.Documents.DocumentClientException: Exception: Microsoft.Azure.Documents.RequestRateTooLargeException, message: {"Errors":[

问题 In Cosmos DB I can (thanks to the SO Community) insert a document like so: data = {'attribute1':1, 'attribute2': 2} client.CreateDocument('dbs/databaseName/colls/collectionName/', data) It would be great if I could insert multiple documents at a time, like how in SQL you can do: insert into table values (1, 2), (3,4), (5,6) I understand that you can do bulk uploads with stored procedures, but if I could basically concat a bunch of documents together I think that would work better for me (..

问题 Im coming from using mongoDB so will use this as an example, in it I can do something like. collection.ensureIndex('id', {unique: true, dropDups: true }); And then whenever I try to insert data with the same id, I will get a duplicate key error and it wont work. great! But can a similar thing be done with documentDB? Currently I have the following code written with node.js to insert data: client.createDocument(collection_id, data_to_insert, function (err, doc) { callback(err, doc); }); 回答1:

问题 Is it possible to use javascript promises instead of regular callbacks within CosmosDB (DocumentDB) stored procedure API calls? An usage would be implementing pagination. For example token = getToken(); doSomething(token); //.... function getToken(....) { //... collection.queryDocuments(link, query, queryOptions, function(error, documents, responseOptions) { return responseOptions.continuation; }); } would not work because the token is returned within a callback, and the execution continues.

问题 I'm curious how the scaling working on the Azure Functions with relation to outputting to Document DB. Basically what happens when Document DB returns a 429 because I'm exceeded my allocated throughput? I ask because when I had the lowest level of Azure Functions combined with the lowest level of Document DB and proceeded to call the function 1000 times in 20 sec I was only seeing 700-800 actual documents inserted into my document db collection. When I scaled Document DB up to the max with

问题 Is there a way to recursively call stored procedures (or even UDFs if that will work) against DocumentDB documents? We have a document that looks something like this: { "docID" : "my_id", "owner" : "fred", "items" : [ { "itemID" : "1", "type" : "item", "value" : 3 }, { "itemID" : "2", "type" : "group", "items" : [ { "itemID" : "2.1", "type" : "group", "items" : [ { "itemID" : "2.1.1", "type" : "item", "value" : 2 }, { "itemID" : "2.1.2", "type" : "item", "value" : 4 } ] }, { "itemID" : "2.2",