Question

A developer notices that a frequently executed query filtering on 'c.status = "active"' has a high RU charge. Using the Query Metrics from the SDK response, they observe that the 'Index Hit Document Count' is much lower than the 'Retrieved Document Count', and 'Index Lookup Time' is minimal while 'Document Load Time' dominates. What is the most likely cause and appropriate remediation?

Accepted Answer

The query engine is performing a full scan because the 'status' path is not indexed; add a range index for '/status/?' to the indexing policy.

Answer

The integrated cache is disabled; provision a dedicated gateway to cache the query results and reduce RU charge.

Answer

The container uses autoscale throughput; switch to manual provisioned throughput to lower the per-query RU cost.

Answer

The partition key is poorly chosen; change the partition key to '/status' so the query targets a single partition.