azure-cosmosdb-mongoapi

问题 Is bulk import available for Azure cosmos db(Mongo db API)? I want to import large dataset set which is available in a json file to Azure cosmos for Mongo DB. I tried importing using mongoimport and Java mongo APIs but it took a long time and timed out in the end. Any suggestions on how to import it directly from my file to cosmos db? PS: https://docs.microsoft.com/en-us/azure/cosmos-db/bulk-executor-java --- says bulk executor is not available for cosmos's mongo db yet. 回答1: Bulk executor

问题 When I'm trying to add a new collection to database I'm getting this error : Failed to create collection 'Products'. Error: Sorry, we are currently experiencing high demand in this region, and cannot fulfill your request at this time. We work continuously to bring more and more capacity online, and encourage you to try again. Please do not hesitate to email docdbswat@microsoft.com at any time or for any reason. ActivityId: bad1a40a-0000-0000-0000-000000000000, Microsoft.Azure.Documents.Common

问题 When I'm trying to add a new collection to database I'm getting this error : Failed to create collection 'Products'. Error: Sorry, we are currently experiencing high demand in this region, and cannot fulfill your request at this time. We work continuously to bring more and more capacity online, and encourage you to try again. Please do not hesitate to email docdbswat@microsoft.com at any time or for any reason. ActivityId: bad1a40a-0000-0000-0000-000000000000, Microsoft.Azure.Documents.Common

问题 When I'm trying to add a new collection to database I'm getting this error : Failed to create collection 'Products'. Error: Sorry, we are currently experiencing high demand in this region, and cannot fulfill your request at this time. We work continuously to bring more and more capacity online, and encourage you to try again. Please do not hesitate to email docdbswat@microsoft.com at any time or for any reason. ActivityId: bad1a40a-0000-0000-0000-000000000000, Microsoft.Azure.Documents.Common

来源： https://stackoverflow.com/questions/63900885/importing-to-cosmosdb-mongodb-api-using-mongorestore-fails-with-retryable-writes

来源： https://stackoverflow.com/questions/63900885/importing-to-cosmosdb-mongodb-api-using-mongorestore-fails-with-retryable-writes

问题 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

问题 I am retrieving my azure cosmosdb/mongodb document from a custom trigger to azure functions.. But my objectId seems to be encrypted.. How to get the correct objectid.. for example ObjectId("5df88e60d588f00c32a3c9ce") is coming as ]øŽ`Õˆð2£ÉÎ or ObjectId("5df88f92d588f00c32a3c9d1") is coming as ]ø’Õˆð2£ÉÑ Is there a way to retrieve objectid in nodejs/python or any script if i give ]ø’Õˆð2£ÉÑ as input. This is my function.json used in the azure function { "scriptFile": "__init__.py", "bindings"

问题 I have a CosmosDB setup using the Mongo API. I have a collection with a hashed shard on one of the field of the document. When I run commands like db.collection.remove or db.collection.deleteMany I get the following error. Command deleteMany failed: query in command must target a single shard key.: {"message":"Command deleteMany failed: query in command must target a single shard key."} I'm not sure how can I mention a shard key as part of the query considering I want the query to run across

问题 I have a MongoDB database in Azure (registered under a Cosmos DB account) and I read on ms docs that the size limit per document stored is 2MB. However, when I try to store an image buffer that is around 1.7 MB I get the following error: 2019-11-01T00:43:14.057681416Z { MongoError: Message: {"Errors":["Request size is too large"]} 2019-11-01T00:43:14.057757320Z RequestStartTime: 2019-11-01T00:43:13.9695930Z, RequestEndTime: 2019-11-01T00:43:13.9995776Z, Number of regions attempted:1 2019-11