support COUNT of a query on a partitioned collection
db.collection.count() works just find but when attempting to count a filtered down collection db.collection.find({query...}).count() results in an Operation Failure that says 'query in command must target a single shard key' but need to be able to do counts across multiple partitions
Mark
shared this idea
This feature is now available. To learn more about this feature and our overall wire protocol support for MongoDB API please see, https://docs.microsoft.com/en-us/azure/cosmos-db/mongodb-feature-support.
Thank you for your suggestion and votes.
24 comments
-
Daniel
commented
Hello,
The main question said:
- need to be able to do counts across multiple partitions.
In my case i also need the operation with ->
db.collection.find({query...}).count()
because my shard key is the ID. If i use aggregation pipeline the RUs is very expensive, how i said in other comment:
- aggregation and consumes more than 30k RUs (with 50k of documents) with match , order and count.
This cost not is possible to asume.
I hope that soon will be possible do this count operation with cross partition.
I believe the status of this feature should not be 'finished', honestly
-
Cristina
commented
Hello. When will it be available for cross-partition queries?
-
Hello. Yes the query should work. Keep in mind this is not a cross-partition query. Only in partition at this time.
-
proxy
commented
Hi ADMIN, you said that this feature is now avaiable, does this mean db.collection.find({query...}).count() can work?
-
Peter
commented
Hi Azure team, any update??
-
Richa Garg
commented
Hi Azure team . I need to query count with filters . I see the issue 'query in command must target a single shard key' still exists . Can you please let me know if this is still work in progress ?
-
Anonymous
commented
Hi Admin, Can we know the exact release date of the api.we need it
-
Sachin
commented
This is really needed. As a workaround since I am only interested in counts for investigative purposes against a DB, I use `db.vacancies.find().toArray().length` in a MongoShell/Robo3T
-
Pablo Mario Everis
commented
This suggestion is really necessary
-
David aguado
commented
Great idea
-
Daniel Vázquez Jiménez
commented
Currently I make this query with aggregation and consumes more than 30k RUS (50k documents) with match, order and count.
This means that we constantly get many errors type: Request rate large.
This feature is very necessary.
-
Prasanna Kumari
commented
This is a required feature and will be very useful.
-
alex
commented
similarly, can you address it for .remove({}) ?
-
Abe
commented
This is a huge shortcoming that is preventing Cosmos from being a real player in the cloud database field. Please address it as quickly as possible.
-
alex
commented
This needs to get fixed.
With the SQL API, you can Enable Cross Partition Queries.
We either need this to work out of the box for the Mongo API or some way to override the restriction similar to the above flag.
-
Mile
commented
This is MAJOR
-
Jeff
commented
This was a major let down.
-
Dewi Felstead
commented
You can achieve a count across partitions using the aggregation pipeline but is proves expensive in terms of RUs (roughly 13K RU to search a collection containing 30K documents using 1 filter condition) so we too would love to have a solution that avoids the use of the aggregation framework.
db.collection.aggregate([{"$match": { fieldName: "fieldValue"}}, {"$count": "countOfDocuments"}])
-
Thiago Cabral commented
I'm with the same problem. Apparently there is no way to update or aggregate if you do not use the shard key in the query.
-
Ignacy
commented
I'm also blocked by that, is there any way to execute query like: "db.collection.updateOne({"_id": ObjectId("abcdefgh1234")}, {"$set": {params}})". Seems to fail on doing find with query, whatever way of updating a record I choose.