cosmos | A minimal toolkit for Solidity contracts | Cryptocurrency library

I'm trying to use golang to do CURD operation in Azure Cosmos db using github.com/vippsas/go-cosmosdb package.

Everything works fine except trying to Create、Replace documents with chinese character in the x-ms-documentdb-partitionkey.

Document sample data, partition key is /method

I am using ADF as a pipeline for writing data from Cosmos to Kusto database by writing following activity:

1. Create temp table in Kusto database.
2. Copy data from cosmos to temp table.
3. Delete the original table, if exist in Kusto database.
4. Rename temp table to original table.

All these changes are part of JSON file from my GIT repo.

I read online that debug process in ADF does not published the changes, so I am not able to see changes in my Kusto database(temp table creation, data copy, old table deletion, renaming of temp table).

How and where to see all the changes done during Debug process of pipeline in ADF and validate(Verify that the correct table name is created and the data is dump properly in the temp table)?

I have a very simple Cosmos DB query that I am making from an asp.net core 3 Razor Pages application. The same query I make in Data Explorer in Azure will return results in 0.02ms. When I run it through the application, setting up stopwatches to see the duration of the calls, it can be anywhere from 400ms to 2000ms.

Like the Title says, I am trying to read an online data file that is in .tbl format. Here is the link to the data: https://irsa.ipac.caltech.edu/data/COSMOS/tables/morphology/cosmos_morph_cassata_1.1.tbl

I tried the following code

I have this JSON file within the Items in a Cosmos DB Container hosted in Azure.

Is there any option in Azure Data Factory to know the list of collections available in a particular database in Azure cosmos account?

Want to execute the particular activity - which returns list of collections in a cosmos db, every time when the Azure Data Factory pipeline get executed.

Exact requirement: Want to do copy data from all the collections from cosmos db but the list of collections in the cosmos db may vary as the time progress. If any new collection has been added to the cosmos db, dynamically that new collection needs to be considered as part of the copy activity without any external intervention.

While using Azure function activity in Azure Data factory to query the list of cosmos collection, it returns output like the below,

i'm making a migration from Table Storage to Cosmos DB. I've created a serveless Cosmos DB (Table Azure)

When i execute the below code

I'm using Azure Cosmos DB 4.0 with MongoDB C# Driver 2.10.4.

Most of the times the queries work fine, but I'm getting intermittent errors like this:

MongoDB.Driver.MongoConnectionException: An exception occurred while sending a message to the server. System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.BeginSend(... at System.Net.Sockets.NetworkStream.BeginWrite --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.BeginWrite at System.Net.Security._SslStream.StartWriting at System.Net.Security._SslStream.ProcessWrite at System.Net.Security._SslStream.BeginWrite

When that error happens the call takes 10-25 seconds before failing.

I'm building the MongoClient with new MongoClient(MongoClientSettings.FromConnectionString(cnstr)) and I was using the connectionstring with these arguments ?ssl=true&replicaSet=globaldb&retrywrites=false.

I tried with retryWrites=true (as per Azure Support suggestion) but that didn't help.

I tried different settings and that didn't work either (connect=direct, maxIdleTimeMS=30000, serverSelectionTimeout=5000ms, socketTimeout=10000ms).

What's causing those exceptions?

I am using Azure functions (JavaScript/node) to query and retrieve data from CosmosDB. That works fine. However, I haven't been successful at implementing key vault secrets to store the primary key for cosmosDB. I get the error: