I am trying to design a cosmos db which I am showing below. In my json format below, the majority of items will be uploaded once, then the nested item of “Trades”, will be once per day. In “Trades”, I will have a reference to another container of “price”, which will be updated every few seconds.

I am trying to design a cosmos db which I am showing below. In my json format below, the majority of items will be uploaded once, then the nested item of “Trades”, will be once per day. In “Trades”, I will have a reference to another container of “price”, which will be updated every few seconds.

Closed 12 hours ago.

I’m looking for a way to get the age of a person given it’s date of birth in CosmosDB.
I’ve read on the docs that they’ve recently implemented “computed properties” at container level on this form:

I am using UpsertItemAsync to create a document and I need to get the uri to that created document, is there some replacement for deprecated CreateDocumentUri or I have to do it manually?

I have created many “Faulted” jobs, I don’t know these jobs will incur costs or not. So I want to delete these jobs. But I failed to find the way to do that.

I am storing data in a Cosmos db which looks similar to the example shown below. I need to write a query that will look in the “payload” section to see if a value exists. It is not possible to use the key (eg ‘lastModifiedOn.previousValue’) as these are dynamically created.

My SQL CosmosDB account is configured with Session consistency and a primary + secondary read-only region. The secondary is only used during DR failover, at which point it is promoted to the write region.

I have questions about how Consistency Levels would behave in suboptimal conditions, like a catastrophic failover or replications falling behind.

I have a container in Cosmos DB with around 10 million documents. This is taking around 3 hours to load from Databricks using cosmos.oltp library integration.