Documentdb存储的proc跨分区查询

为每条记录下载1，并在客户端对它们进行总计/计数

Download a 1 for every record and sum/count them client-side

为每个唯一分区键重新运行存储过程.就我而言，这并不像听起来那样糟糕，因为分区键是一个tenantID，而我只有十几个，并且最多只能看到几百个.

Rerun the stored procedure for each unique partition key. In my case, this was not as bad as it sounds since the partition key is a tenantID and I only have a dozen of those and only expect a few hundred max.

我不确定这一点，因为我还没有对分区集合进行尝试，但是现在每个查询都在x-ms-resource-usage标头中返回集合的资源使用情况.该标头具有documentsSize子标头.您可以将其除以文档的平均大小，以获得一个近似的计数.到目前为止，该标头信息中甚至还可能有一个计数记录.

I'm not sure about this one since I haven't tried it with partitioned collections, but each query now returns the resource usage of the collection in the x-ms-resource-usage header. That header has a documentsSize sub-header. You could use that divided by the average size of your documents to get an approximate count. There may even be a count record in that header information by now.

此外，还有一个x-ms-item-count标头，但我不确定它的行为.如果您对整个分区集合中的所有记录发送查询，并将max-item-count设置为1，则只会返回一条记录，因此您不会在RU上花费很多，但我不会知道标题的行为.在这种情况下，它是否返回1?还是返回所有查询页面最终将返回的文档总数，如果您不愿意请求每一页.快速实验应该可以证实这一点.

Also, there is an x-ms-item-count header but I'm not sure how that behaves. If you send a query for all the records in the entire partitioned collection and set the max-item-count to 1, you'll only get back one record and it shouldn't cost you a lot in RUs, but I don't know how that header behaves. Does it return a 1 in that case? Or does it return the total number of documents all the pages of the query would eventually return if you bothered to request every page. A quick experiment should confirm this.