Azure Cosmos DB - V2 Indexing Policy

Asked Dec 20 '19 at 10:37

Active Dec 23 '19 at 09:53

Viewed 203 times

We are having performance issues when using the COUNT function on a container with ~500,000 items.

This query...

SELECT VALUE COUNT(1) FROM c where c.batch = 'TestBatch'

...is slow, and returns a count of 438797, consuming 13438 RUs. I'm running this query using V3 of the Cosmos DB SDK, using a FeedIterator and passing in a single partition key.

I’ve noticed in a few other posts, mentions of a “V2” indexing policy, which apparently includes some significant performance improvements.

How can I check what version of the policy my database is using, and if it’s not V2, how can I upgrade to this?

edited Dec 23 '19 at 09:53

asked Dec 20 '19 at 10:37

Robert Dougan

I mean, what do you expect if your query returns 440k items? – 4c74356b41 Dec 20 '19 at 11:00
Can you post the code that shows how are you consuming that query? And is `batch` your partition key in the collection? – Matias Quaranta Dec 20 '19 at 17:00
@MatiasQuaranta I'm using a FeedIterator and setting the partition key via the QueryRequestOptions that I pass in. "batch" isn't the partition key. – Robert Dougan Dec 23 '19 at 09:48

Azure Cosmos DB - V2 Indexing Policy

0 Answers0