Question

A high-throughput orders container ingests thousands of writes per second. Documents contain dozens of properties, but analysts only ever filter on 'status' and 'customerId', and sort on 'orderDate'. The team notices write RU charges are very high due to the default indexing policy indexing every path. They want to minimize write RU cost while still supporting the known query patterns efficiently. Which indexing policy change best achieves this?

Accepted Answer

Change the includedPaths to only '/status/?', '/customerId/?', and '/orderDate/?', set excludedPaths to '/*', and add a composite index on ('status', 'orderDate').

Answer

Set the indexing mode to 'none' so writes incur no indexing overhead, then rely on cross-partition scans for the analyst queries.

Answer

Keep includedPaths at '/*' and add each frequently queried property to excludedPaths individually.

Answer

Enable wildcard indexing on '/*/?' and disable the automatic indexing flag to reduce write cost.