When I configure the index policy to 'none', I get an error "Indexing mode value cannot be 'none' when 'defaultTtl' is specified in the collection".
Would it be possible to enhance the documentation to explain how to specify a default TTL for a collection that is being used for key-value storage?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@robin-parker Thank you for your feedback! We will review and provide an update as appropriate.
@robin-parker In looking through this, the only very slight reference that an index policy other than None might be required is in the form of a Note: on the documentation page where None should be used with access patterns that require ID or self-link only. It's a stretch but it indicates that without an indexing policy, lookups need to be direct (Indexing modes). If there was an additional note or section that addressed TTL functionality, as there is currently nothing pertaining to indexing policy requirements for TTL functionality.
I am going to assign this issue to the content author to evaluate and update as appropriate. @SnehaGunda for awareness.
We will address it in the docs. Thank you.
@ThomasWeiss has some significant updates to the indexing docs, he will cover this in his updates. We have reached out to the dev team to understand the behavior, will post the response soon.
@robin-parker The TTL feature requires indexing to be active, so either of these will fail indeed:
None while TTL is activatedNone.To use TTL for a collection used as pure key-value pair, you can use the following policy:
{
 "indexingMode": "consistent",
 "automatic": true,
 "includedPaths": [],
 "excludedPaths": [{
  "path": "/*"
 }]
}
Thanks a lot for pointing that out, I'm updating the docs accordingly!
Thanks for the quick response, this is now working just fine.
Most helpful comment
@robin-parker The TTL feature requires indexing to be active, so either of these will fail indeed:
Nonewhile TTL is activatedNone.To use TTL for a collection used as pure key-value pair, you can use the following policy:
Thanks a lot for pointing that out, I'm updating the docs accordingly!
please-close