Editorial question25.5K views1,230 votes0 answers2,999 following
AI-generatedCan a custom indexing policy reduce request-unit costs while preserving range-query performance in Cosmos DB?
Automatic indexing in Azure Cosmos DB for NoSQL indexes every property on write, simplifying schema evolution but consuming request units per operation. When a custom indexing policy excludes specific paths, the default composite index interaction with remaining fields becomes a design consideration, particularly for range and equality queries. The policy ch