Does disabling container-level TTL stop background cleanup of expired items?
An Azure Cosmos DB SQL (Core) API container previously had time-to-live enabled at the container level. Several items already contain expiration timestamp values, and some timestamps have passed while TTL was active. After disabling container-level TTL, it is unclear whether the asynchronous background cleanup continues to remove items whose expiration times
dynamodb
cosmosdb