ttl field on Azure Cosmos DB NOSQL API doesn't appear in documents

Question

ttl field on Azure Cosmos DB NOSQL API doesn't appear in documents

David Pereira 1

Hello,

I have a NOSQL API cosmos DB and I'm trying to use the TTL feature.
However I can't get the ttl field to appear on my documents for my container that has TTL ON.

I have two Azure subscriptions, in one of them I create a NOSQL API cosmos DB and documents appear with the "ttl" field, basically the feature works just fine.
On the other subscription it doesn't work, even when the cosmos DB has the same setup, TTL only works on the container level. If I set the "ttl" field on the document, it doesn't even appear when I try to view it with Data Explorer, but the rest of the document's fields are fine.

What are the reasons the TTL feature could work on some cosmos DB accounts and others don't?
Any idea how I can troubleshoot this?

GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-12-20T19:42:21.367+00:00

Hi,@David Pereira Welcome to the Microsoft Q&A platform, thanks for posting the question
If I understand correctly you have two Azure subscriptions and enabling ttl is working fine for one subscription and doesn't work for the other subscription.
That's a weird predicament, are you sure the configurations are exactly the same? with the same permissions on the account, are you attempting to add TTL on the 2nd account have contributor permissions?

Regards
Geetha
David Pereira 1 Reputation point

2022-12-21T08:39:58.637+00:00

Hi @GeethaThatipatri-MSFT , you raise a good point about permissions and I'm not sure if they are the same.
I'm adding documents to the container in cosmos DB using the C# SDK, and the object that i'm adding has the "ttl" field. In terms of the code it's exactly the same for both accounts, connecting through the connection string.
I exported the ARM template for both cosmos DBs and they are the same on the container I have TTL ON.

It's weird because "ttl" is the only field that doesn't get added on 1 DB, the rest of the document is saved. Do you know what else I can try?

Thanks,
David Pereira.
GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-12-21T21:49:25.613+00:00

@David Pereira Can you please share a screenshot from both for better understanding?

Regards
Geetha

1 answer

Your answer

GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-12-20T19:42:21.367+00:00

Hi,@David Pereira Welcome to the Microsoft Q&A platform, thanks for posting the question
If I understand correctly you have two Azure subscriptions and enabling ttl is working fine for one subscription and doesn't work for the other subscription.
That's a weird predicament, are you sure the configurations are exactly the same? with the same permissions on the account, are you attempting to add TTL on the 2nd account have contributor permissions?

Regards
Geetha
David Pereira 1 Reputation point

2022-12-21T08:39:58.637+00:00

Hi @GeethaThatipatri-MSFT , you raise a good point about permissions and I'm not sure if they are the same.
I'm adding documents to the container in cosmos DB using the C# SDK, and the object that i'm adding has the "ttl" field. In terms of the code it's exactly the same for both accounts, connecting through the connection string.
I exported the ARM template for both cosmos DBs and they are the same on the container I have TTL ON.

It's weird because "ttl" is the only field that doesn't get added on 1 DB, the rest of the document is saved. Do you know what else I can try?

Thanks,
David Pereira.
GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-12-21T21:49:25.613+00:00

@David Pereira Can you please share a screenshot from both for better understanding?

Regards
Geetha

Answer 1

David Pereira 1

Hi Geetha, it appears the problem is resolved without any changes to configuration. Perhaps it had something to do with indexes or "caching", something that prevented the ttl field to appear on the documents the first time. It was an existing container with tons of documents, perhaps changing the settings to TTL ON, updating and then creating documents with the "ttl" field takes some time on cosmos DB to apply.

Nevertheless it's resolved, thanks!

GeethaThatipatri-MSFT 29,542 Reputation points Microsoft Employee Moderator

2022-12-22T16:34:30.303+00:00

@David Pereira Great that your issue got resolved, and thanks for sharing the information here.

Regards
Geetha

Share via

ttl field on Azure Cosmos DB NOSQL API doesn't appear in documents

1 answer

Your answer